Signaling of dormant bandwidth part

ABSTRACT

A method performed by a user equipment, UE, in a wireless communication network is provided. The method includes receiving a bandwidth part, BWP, configuration associated with a BWP of a secondary serving cell, Scell, of the UE. The UE determines whether the BWP of the Scell of the UE is a dormant BWP based on a received higher layer parameter in a Scell configuration that indicates an identifier of the dormant BWP. In response to determining whether the BWP of the Scell is a dormant BWP, the UE determines a set of actions performable by the UE based on whether the BWP is a dormant BWP; and performs the set of actions.

TECHNICAL FIELD

The present disclosure relates generally to communications, and moreparticularly to communication methods and related devices and nodessupporting wireless communications.

BACKGROUND

Carrier Aggregation (CA) can be used in new radio (NR) (5^(th)Generation (5G)) and long term evolution (LTE) systems to improve userequipment (UE) transmit/receive data rate. With CA, the UE can operateinitially on a single serving cell called a primary cell (Pcell). ThePcell can be operated on a component carrier in a frequency band. The UEcan then be configured by the network with one or more secondary servingcells (Scells). Each Scell can correspond to a component carrier (CC) inthe same frequency band (intra-band CA) or different frequency band(inter-band CA) from the frequency band of the CC corresponding to thePcell. For the UE to transmit/receive data on the Scells (e.g., byreceiving downlink link shared channel (DL-SCH) information on aphysical downlink shared channel (PDSCH) or by transmitting uplinkshared channel (UL-SCH) on a physical uplink shared channel (PUSCH)),the Scells may be activated by the network. The Scells can also bedeactivated and later reactivated as needed via activation/deactivationsignaling.

FIG. 1 illustrates an example of Scell activation/deactivation relatedprocedures specified for Rel15 NR. As shown in FIG. 1 , except forchannel state information (CSI) reporting, the UE is allowed to startperforming other activation related actions (e.g., physical downlinkcontrol channel (PDCCH) monitoring for Scell, physical uplink controlchannel (PUCCH)/sounding reference signal (SRS) transmission on theScell) within a specified range of slots (e.g., after the minimumrequired activation delay (specified in 38.213) and before the maximumallowed activation delay (specified in 38.133)). CSI reporting for theScell can start/stops with a fixed slot offset after receiving theactivation/deactivation command.

In slot 110, the Scell activation command (MCC CE) is received. In slot120, the UE starts CSI reporting for the Scell. OOR is reported untilScell is not activated. UE may start PDCCH monitoring and apply other‘activation’ related actions from this slot. In slot 130, UE startsPDCCH monitoring and apply other ‘activation’ related actions describedin 38.321 subclause 5.9. In slot 140, Scell deactivation command (MCCCE) is received. UE may stop PDCCH monitoring and apply other‘deactivation’ related actions from this slot. In slot 150, the UE stopsPDCCH monitoring and apply other ‘deactivation’ related actionsdescribed in 38.321 subclause 5.9. In slot 160, UE stops CSI reportingfor the Scell.

A minimum required activation delay and maximum allowed activation delayfor some example conditions are described below.

A Minimum required activation delay can be k1+3 ms+1 slots as specified38.213 sub clause 4.3. Assuming 30 kHz numerology for Pcell, and k1=4,this would be 5.5 ms.

A Maximum allowed activation delay can depend on conditions described in38.133 sub clause 8.3.2 and the value can vary based on UE measurementconfiguration, operating frequency range, and other aspects. Forexample, assuming T_HARQ in 38.133 has similar meaning as k1 in 38.213,and assuming ‘known Scell’ with Scell measurement cycle is equal to orsmaller than [160 ms], and T_csi_reporting=4 slots, for FR1 and 30 kHzSCS, if SMTC periodicity 5 ms, the delay cannot be larger than (T_HARQ=4slots)+(T_act_time=5 ms+5 ms)+(T_csi_report=4 slots)=14 ms. If SMTCperiodicity 20 ms, the delay cannot be larger than (T_HARQ=4slots)+(T_act_time=5 ms+20 ms)+(T_csi_report=4 slots)=29 ms. For FR2,assuming this is the first Scell being activated in that FR2 band, ifSMTC periodicity is 5 ms, the delay is 4 slots+5 ms+TBD*5 ms+4 slots=6ms+X*5 ms. If SMTC periodicity is 20 ms, the delay is 4 slots+5ms+TBD*20 ms+4 slots=6 ms+X*20 ms. Rel15 specs may define the delay ifX>1.

For other conditions (e.g., Scell is not ‘known’ and longer SMTCperiodicities), the maximum allowed activation delay can be longer thanthe values in the above examples.

In NR, a subset of the total cell bandwidth of a cell can be referred toas a Bandwidth Part (BWP) and bandwidth adaptation can be achieved byconfiguring the UE with BWP(s) and telling the UE which of theconfigured BWPs is currently the active one.

FIG. 2 illustrates a scenario where 3 different BWPs are configured.BWP₁ has a width of 40 MHz and subcarrier spacing of 15 kHz. BWP₂ has awidth of 10 MHz and subcarrier spacing of 15 kHz. BWP₃ has a width of 20MHz and subcarrier spacing of 60 kHz.

In NR, two options for configuring BWP #0 (initial BWP) were specified(i.e., Option 1 and Option 2 described in Annex B.2 of 38.331). When theBWP configuration includes UE-specific information that BWP can beconsidered as a UE-specific radio resource control (RRC) configured BWP

SUMMARY

According to some embodiments, a method performed by a user equipment ina wireless communication network is provided. The method includesreceiving a bandwidth part, BWP, configuration associated with a BWP ofa secondary serving cell, Scell, of the UE. The method further includesdetermining whether the BWP of the Scell of the UE is a dormant BWPbased on whether a field of the BWP configuration indicates the BWP is adormant BWP. The method further includes responsive to determiningwhether the BWP of the Scell is a dormant BWP, determining (850) a setof actions performable by the UE based on whether the BWP is a dormantBWP. The method further includes performing the set of actions.

According to other embodiments, a method performed by a network node ina wireless communication network is provided. The method includesdetermining a dormant bandwidth part, BWP, configuration associated witha dormant BWP of a secondary cell, Scell, of a user equipment, UE. Themethod further includes transmitting a command to cause the UE to switchbetween the dormant BWP and another BWP of the Scell.

According to other embodiments, a user equipment, UE, configured tooperate in a wireless communication network is provided. The UE includesprocessing circuitry and memory coupled to the processing circuitry. Thememory has instructions stored therein that are executable by theprocessing circuitry to cause the UE to perform operations. Theoperations include receiving a bandwidth part, BWP, configurationassociated with a BWP of a secondary serving cell, Scell, of the UE. Theoperations further include determining whether the BWP of the Scell ofthe UE is a dormant BWP based on whether a field of the BWPconfiguration indicates the BWP is a dormant BWP. The operations furtherinclude, responsive to determining whether the BWP of the Scell is adormant BWP, determining a set of actions performable by the UE based onwhether the BWP is a dormant BWP. The operations further includeperforming the set of actions.

According to other embodiments, a network node configured to operate ina wireless communication network is provided. The network node includesprocessing circuitry and memory coupled to the processing circuitry. Thememory has instructions stored therein that are executable by theprocessing circuitry to cause the network node to perform operations.The operations include determining a dormant bandwidth part, BWP,configuration associated with a dormant BWP of a secondary cell, Scell,of a user equipment, UE. The operations further include transmitting acommand to cause the UE to switch between the dormant BWP and anotherBWP of the Scell.

In other embodiments, a user equipment, UE, configured to operate in awireless communication network is provided. The UE is adapted to performoperations. The operations include receiving a bandwidth part, BWP,configuration associated with a BWP of a secondary serving cell, Scell,of the UE. The operations further include determining whether the BWP ofthe Scell of the UE is a dormant BWP based on whether a field of the BWPconfiguration indicates the BWP is a dormant BWP. The operations furtherinclude, responsive to determining whether the BWP of the Scell is adormant BWP, determining a set of actions performable by the UE based onwhether the BWP is a dormant BWP. The operations further includeperforming the set of actions.

In other embodiments, a network node configured to operate in a wirelesscommunication network is provided. The network node is adapted toperform operations. The operations include determining a dormantbandwidth part, BWP, configuration associated with a dormant BWP of asecondary cell, Scell, of a user equipment, UE. The operations furtherinclude transmitting a command to cause the UE to switch between thedormant BWP and another BWP of the Scell.

In other embodiments, a computer program is provided. The computerprogram includes program code to be executed by processing circuitry ofa user equipment, UE, configured to operate in a wireless communicationnetwork. Execution of the program code causes the UE to performoperations. The operations include receiving a bandwidth part, BWP,configuration associated with a BWP of a secondary serving cell, Scell,of the UE. The operations further include determining whether the BWP ofthe Scell of the UE is a dormant BWP based on whether a field of the BWPconfiguration indicates the BWP is a dormant BWP. The operations furtherinclude, responsive to determining whether the BWP of the Scell is adormant BWP, determining a set of actions performable by the UE based onwhether the BWP is a dormant BWP. The operations further includeperforming the set of actions.

According to other embodiments, a computer program is provided. Thecomputer program includes program code to be executed by processingcircuitry of a network node configured to operate in a wirelesscommunication network. Execution of the program code causes the networknode to perform operations. The operations include determining a dormantbandwidth part, BWP, configuration associated with a dormant BWP of asecondary cell, Scell, of a user equipment, UE. The operations furtherinclude transmitting a command to cause the UE to switch between thedormant BWP and another BWP of the Scell.

According to other embodiments, a computer program product is provided.The computer program product includes a non-transitory storage mediumincluding program code to be executed by processing circuitry of a userequipment, UE, configured to operate in a wireless communicationnetwork. Execution of the program code causes the UE to performoperations. The operations include receiving a bandwidth part, BWP,configuration associated with a BWP of a secondary serving cell, Scell,of the UE. The operations further include determining whether the BWP ofthe Scell of the UE is a dormant BWP based on whether a field of the BWPconfiguration indicates the BWP is a dormant BWP. The operations furtherinclude, responsive to determining whether the BWP of the Scell is adormant BWP, determining a set of actions performable by the UE based onwhether the BWP is a dormant BWP. The operations further includeperforming the set of actions.

According to other embodiments, a computer program product is provided.The computer program product includes a non-transitory storage mediumincluding program code to be executed by processing circuitry of anetwork node configured to operate in a wireless communication network.Execution of the program code causes the network node to performoperations. The operations include determining a dormant bandwidth part,BWP, configuration associated with a dormant BWP of a secondary cell,Scell, of a user equipment, UE. The operations further includetransmitting a command to cause the UE to switch between the dormant BWPand another BWP of the Scell.

Various embodiments described herein allow a UE to detect a BWP is adormant BWP and indicates actions to be taken by a UE in a dormant BWP.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the disclosure and are incorporated in and constitute apart of this application, illustrate certain non-limiting embodiments ofinventive concepts. In the drawings:

FIG. 1 is a schematic diagram illustrating an example Scellactivation/deactivation related procedures;

FIG. 2 is a graph illustrating an example of a scenario where threedifferent BWPs are configured according to some embodiments of inventiveconcepts;

FIG. 3 is a block diagram illustrating an example of BWP #0configuration without dedicated configuration according to someembodiments of inventive concepts;

FIG. 4 is a block diagram illustrating an example of BWP #0configuration with dedicated configuration according to some embodimentsof inventive concepts;

FIG. 5 is a block diagram illustrating a wireless device (UE) accordingto some embodiments of inventive concepts;

FIG. 6 is a block diagram illustrating a radio access network (RAN) nodeaccording to some embodiments of inventive concepts;

FIG. 7 is a block diagram illustrating a CN (CN) node according to someembodiments of inventive concepts;

FIGS. 8-11 are flow charts illustrating examples of operations of a UEaccording to some embodiments of inventive concepts;

FIG. 12 is a flow chart illustrating an example of operations of anetwork node according to some embodiments of inventive concepts;

FIG. 13 is a block diagram of a wireless network in accordance with someembodiments;

FIG. 14 is a block diagram of a user equipment in accordance with someembodiments

FIG. 15 is a block diagram of a virtualization environment in accordancewith some embodiments;

FIG. 16 is a block diagram of a telecommunication network connected viaan intermediate network to a host computer in accordance with someembodiments;

FIG. 17 is a block diagram of a host computer communicating via a basestation with a user equipment over a partially wireless connection inaccordance with some embodiments;

FIG. 18 is a block diagram of methods implemented in a communicationsystem including a host computer, a base station and a user equipment inaccordance with some embodiments;

FIG. 19 is a block diagram of methods implemented in a communicationsystem including a host computer, a base station and a user equipment inaccordance with some embodiments;

FIG. 20 is a block diagram of methods implemented in a communicationsystem including a host computer, a base station and a user equipment inaccordance with some embodiments; and

FIG. 21 is a block diagram of methods implemented in a communicationsystem including a host computer, a base station and a user equipment inaccordance with some embodiments.

DETAILED DESCRIPTION

Inventive concepts will now be described more fully hereinafter withreference to the accompanying drawings, in which examples of embodimentsof inventive concepts are shown. Inventive concepts may, however, beembodied in many different forms and should not be construed as limitedto the embodiments set forth herein. Rather, these embodiments areprovided so that this disclosure will be thorough and complete, and willfully convey the scope of present inventive concepts to those skilled inthe art. It should also be noted that these embodiments are not mutuallyexclusive. Components from one embodiment may be tacitly assumed to bepresent/used in another embodiment.

The following description presents various embodiments of the disclosedsubject matter. These embodiments are presented as teaching examples andare not to be construed as limiting the scope of the disclosed subjectmatter. For example, certain details of the described embodiments may bemodified, omitted, or expanded upon without departing from the scope ofthe described subject matter.

FIG. 5 is a block diagram illustrating elements of a wireless device UE1000 (also referred to as a mobile terminal, a mobile communicationterminal, a wireless communication device, a wireless terminal, mobiledevice, a wireless communication terminal, user equipment, UE, a userequipment node/terminal/device, etc.) configured to provide wirelesscommunication according to embodiments of inventive concepts. (Wirelessdevice 1000 may be provided, for example, as discussed below withrespect to wireless device 4110 of FIG. 13 , UE 4200 of FIG. 14 , UEs4491, 4492 of FIG. 16 , and/or UE 4530 of FIG. 17 .) As shown, wirelessdevice UE may include an antenna 1007 (e.g., corresponding to antenna4111 of FIG. 13 ), and transceiver circuitry 501 (also referred to as atransceiver, e.g., corresponding to interface 4114 of FIG. 13 ,interfaces 4205, 4209, 4211, transmitter 4233, and receiver 4235 of FIG.14 , and radio interface 4537 of FIG. 17 ) including a transmitter and areceiver configured to provide uplink and downlink radio communicationswith a base station(s) (e.g., corresponding to network node 4160 of FIG.13 , also referred to as a RAN node) of a radio access network. Wirelessdevice UE may also include processing circuitry 503 (also referred to asa processor, e.g., corresponding to processing circuitry 4120 of FIG. 13, processor 4201 of FIG. 14 , and processing circuitry 4538 of FIG. 17 )coupled to the transceiver circuitry, and memory circuitry 505 (alsoreferred to as memory, e.g., corresponding to device readable medium4130 of FIG. 13 ) coupled to the processing circuitry. The memorycircuitry 505 may include computer readable program code that whenexecuted by the processing circuitry 503 causes the processing circuitryto perform operations according to embodiments disclosed herein.According to other embodiments, processing circuitry 503 may be definedto include memory so that separate memory circuitry is not required.Wireless device UE may also include an interface (such as a userinterface) coupled with processing circuitry 503, and/or wireless deviceUE may be incorporated in a vehicle.

As discussed herein, operations of wireless device UE may be performedby processing circuitry 503 and/or transceiver circuitry 501. Forexample, processing circuitry 503 may control transceiver circuitry 501to transmit communications through transceiver circuitry 501 over aradio interface to a radio access network node (also referred to as abase station) and/or to receive communications through transceivercircuitry 501 from a RAN node over a radio interface. Moreover, modulesmay be stored in memory circuitry 505, and these modules may provideinstructions so that when instructions of a module are executed byprocessing circuitry 503, processing circuitry 503 performs respectiveoperations (e.g., operations discussed below with respect to ExampleEmbodiments relating to wireless devices).

FIG. 6 is a block diagram illustrating elements of a radio accessnetwork RAN node 600 (also referred to as a network node, base station,eNodeB/eNB, gNodeB/gNB, etc.) of a Radio Access Network (RAN) configuredto provide cellular communication according to embodiments of inventiveconcepts. (RAN node 600 may be provided, for example, as discussed belowwith respect to network node 4160 of FIG. 13 , base stations 4412 a,4412 b, 4412 c of FIG. 16 , and/or base station 4520 of FIG. 17 .) Asshown, the RAN node may include transceiver circuitry 601 (also referredto as a transceiver, e.g., corresponding to portions of interface 4190of FIG. 13 and/or portions of radio interface 4527 of FIG. 17 )including a transmitter and a receiver configured to provide uplink anddownlink radio communications with mobile terminals. The RAN node mayinclude network interface circuitry 607 (also referred to as a networkinterface, e.g., corresponding to portions of interface 4190 of FIG. 13and/or portions of communication interface 4526 of FIG. 17 ) configuredto provide communications with other nodes (e.g., with other basestations) of the RAN and/or core network CN. The network node may alsoinclude processing circuitry 603 (also referred to as a processor, e.g.,corresponding to processing circuitry 4170 of FIG. 13 and/or processingcircuitry 4528 of FIG. 17 ) coupled to the transceiver circuitry, andmemory circuitry 605 (also referred to as memory, e.g., corresponding todevice readable medium 4180 of FIG. 13 ) coupled to the processingcircuitry. The memory circuitry 605 may include computer readableprogram code that when executed by the processing circuitry 603 causesthe processing circuitry to perform operations according to embodimentsdisclosed herein. According to other embodiments, processing circuitry603 may be defined to include memory so that a separate memory circuitryis not required.

As discussed herein, operations of the RAN node may be performed byprocessing circuitry 603, network interface 607, and/or transceiver 601.For example, processing circuitry 603 may control transceiver 601 totransmit downlink communications through transceiver 601 over a radiointerface to one or more mobile terminals UEs and/or to receive uplinkcommunications through transceiver 601 from one or more mobile terminalsUEs over a radio interface. Similarly, processing circuitry 603 maycontrol network interface 607 to transmit communications through networkinterface 607 to one or more other network nodes and/or to receivecommunications through network interface from one or more other networknodes. Moreover, modules may be stored in memory 605, and these modulesmay provide instructions so that when instructions of a module areexecuted by processing circuitry 603, processing circuitry 603 performsrespective operations (e.g., operations discussed below with respect toExample Embodiments relating to RAN nodes).

According to some other embodiments, a network node may be implementedas a core network CN node without a transceiver. In such embodiments,transmission to a wireless device UE may be initiated by the networknode so that transmission to the wireless device is provided through anetwork node including a transceiver (e.g., through a base station orRAN node). According to embodiments where the network node is a RAN nodeincluding a transceiver, initiating transmission may includetransmitting through the transceiver.

FIG. 7 is a block diagram illustrating elements of a core network CNnode (e.g., an SMF node, an AMF node, etc.) of a communication networkconfigured to provide cellular communication according to embodiments ofinventive concepts. As shown, the CN node may include network interfacecircuitry 707 (also referred to as a network interface) configured toprovide communications with other nodes of the core network and/or theradio access network RAN. The CN node may also include a processingcircuitry 703 (also referred to as a processor) coupled to the networkinterface circuitry, and memory circuitry 705 (also referred to asmemory) coupled to the processing circuitry. The memory circuitry 705may include computer readable program code that when executed by theprocessing circuitry 703 causes the processing circuitry to performoperations according to embodiments disclosed herein. According to otherembodiments, processing circuitry 703 may be defined to include memoryso that a separate memory circuitry is not required.

As discussed herein, operations of the CN node may be performed byprocessing circuitry 703 and/or network interface circuitry 707. Forexample, processing circuitry 703 may control network interfacecircuitry 707 to transmit communications through network interfacecircuitry 707 to one or more other network nodes and/or to receivecommunications through network interface circuitry from one or moreother network nodes. Moreover, modules may be stored in memory 705, andthese modules may provide instructions so that when instructions of amodule are executed by processing circuitry 703, processing circuitry703 performs respective operations (e.g., operations discussed belowwith respect to Example Embodiments relating to core network nodes).

In NR Rel15, a Downlink Control Information (DCI) based BWP switchingmechanism can be defined. The DCI based BWP can be used by the UE toswitch between two different BWPs on a serving cell x. For NR Rel16, theBWP switching mechanism may be used to indicate transition to/fromdormancy behaviour on activated Scells. The indication for thetransition can be sent on the Pcell. To indicate transition to dormancy,the UE can be switched to a specific BWP generally referred to asdormant BWP.

Various embodiments described herein provide mechanisms for efficientconfiguration and signalling of dormant BWP for transitioning SCellsto/from dormancy. Various signalling approaches to configure a dormantBWP and to differentiate a dormant BWP from other UE-specificallyconfigured BWPs are provided.

Some embodiments enable use of dormant BWP on an Scell withoutincreasing the DCI overhead of the PDCCHs received on the Scell.Additional or alternative embodiments, allow controlling certainperiodic UL transmissions on an Scell (e.g. SRS transmissions) using thedormant BWP framework with less signalling overhead.

In some embodiments, a UE communicates with the network using a primaryserving cell (Pcell). The UE can be configured with one or moresecondary serving cells (Scells). The UE can receive a higher layerScell activation/deactivation command. Upon reception of the higherlayer activation/deactivation command, the UE can start/stop performinga first set of actions. The first set of actions can include periodicCSI reporting for the Scell (e.g., if the UE is configured for periodicCSI reporting). The first set of actions can also include PDCCHmonitoring on the Scell. If the UE is configured with multiple BWPs forthe Scell, the PDCCH monitoring can be on a preconfigured/default BWP ofthe Scell. If the UE receives the higher layer activation command intime slot n, the UE applies the first set of actions starting with slotn+D1 (i.e., after an activation delay of D1 slots). The UE also receivesa physical layer command (L1 command). Upon reception of the L1 command,the UE starts/stops performing a second set of actions. The second setof actions can be PDCCH monitoring or BWP switching. The second set ofactions can be triggered by switching the UE to a specific BWP on theSCell. The specific BWP can be a dormant BWP.

In some embodiments, switching to a dormant BWP (transitioning to adormancy-like behavior on the activated Scell) can include stoppingPDCCH monitoring on an activated Scell (e.g. second set of actions) butcontinuing to perform CSI reporting for the SCell. For example, theScell can be activated via a MAC/CE (higher layer activation command)upon reception of which the UE can start PDCCH monitoring on Scell andCSI reporting for the Scell (e.g. first set of actions). Upon receptionof the L1 command, the UE may stop PDCCH monitoring on the Scell (e.g.second set of actions) by switching to a dormant BWP which is configuredwithout PDCCH monitoring.

If the UE receives the L1 command in time slot n1, the UE can apply thesecond set of actions (or transitions to dormancy like behavior, orswitches to dormant BWP) starting with slot n1+D2 (i.e., after a delayof D2 slots). The delay D2 can be smaller than D1.

The higher layer Scell activation/deactivation command can be receivedby the UE in a MAC CE (MAC control element). The first set of actionscan also include transmitting PUCCH/periodic SRS on the Scell.

The L1 command can be received by the UE using a PDCCH. For example, theL1 command can be part of PDCCH DCI (downlink control information). ThePDCCH DCI corresponding to the L1 command can include the bitscorresponding to the Scells configured for the UE. Based on the L1command on the Pcell the UE can switch to a dormant BWP on the Scell.

The dormant BWP can be a BWP with at least the followingcharacteristics. The dormant BWP can be configured without PDCCHmonitoring (e.g. the IE pdcch-Config is absent in the BWPconfiguration). The dormant BWP can be configured only when UE isconfigured with at least one other UE-specific RRC configured BWP (i.e.,a ‘regular BWP’). The UE determines via RRC configuration, which DL BWPamong the UE-specific RRC configured BWPs is the dormant BWP.

In addition to the above, BWP #0 (or initial BWP) may not be assumed asdormant BWP at least for the case of BWP #0 configuration withoutdedicated configuration (i.e., Option 1 in 38.331) For identifying thedormant BWP among the RRC configured BWPs, one option would be toconfigure the dormant BWP ID explicitly via RRC (e.g., a new fielddormantBWP-Id as part of ServingCellConfig).

In some embodiments, the network may have a restriction that only oneBWP among the RRC configured BWPs can be configured without PDCCHmonitoring, and BWP ID of that BWP is implicitly assumed as dormant BWP.

In additional or alternative embodiments, a new field can be introduced(e.g., dormantBWP-Idreference) that can allow for configuration of a BWPID as a reference to specific BWPs that can be used to identify adormant BWP configuration. The UE can assume that dormant BWP hasidentical configuration as the reference BWP except for somepredefined/prespecified such as PDCCH monitoring and SRS transmission.For example, the UE does not perform PDCCH monitoring and SRStransmission when switched to dormant BWP.

In additional or alternative embodiments, a new parameter fieldisDormantBWP is introduced within BWP configuration and if the parameteris set to ‘true’, it denotes the corresponding BWP is a dormant BWP, andif the parameter is absent or set to ‘false’, the corresponding BWP isnot considered as a dormant BWP (e.g., considered a regular BWP).

When dormant BWP is configured for an Scell, in most cases it increasesthe DCI payload size for the Scell by 1 additional bit for the“Bandwidth part indicator” field. For example, assuming Option 2 BWP #0configuration, without a dormant BWP it is possible to operate a Scellwith 0 bit BWP indicator field, but configuring a dormant BWP wouldrequire a 1 bit field. Similarly, with Option 1 BWP #0 configuration,the 1 bit field may need to be increased to two bits.

Since switching to/from dormant BWP is already indicated on Pcell, theadditional bit in the Scell DCI may be redundant. For example, if oneextra bit is added to Pcell DCI to indicate transition to/from dormantBWP of the Scell, in principle there is no need to have one more extrabit in the Scell DCI when the extra bit in Pcell DCI is always present.Also for cases where the dormant BWP is configured to be same as defaultBWP, the BWP inactivity timer provides another option to switch todormant BWP, which may make the extra bit redundant. This extra overheadcan be avoided by not considering the dormant BWP as part of the numberof BWPs (n_(BWP,RRC)) configured by higher layers while determining DCIpayload of the Scells (i.e., considering only those BWPs that are notconfigured as dormant BWP for DCI payload calculation)

In some embodiments, whether the dormant BWP is considered or not whendetermining the size of BWP indicator field for the Scell DCI can bebased on one or more of below criteria. The dormant BWP can beconsidered only if its BWP ID is in a certain range. For example, if BWPID of dormant BWP is configured to be <=4, it is considered, otherwiseit is not considered. The dormant BWP can be considered or not based onthe payload size of the DCI field used for Scell dormancy indication onthe Pcell. For example, if the payload size of the Pcell DCI field is >0bits, the BWP ID of dormant BWP is considered for determining the sizeof BWP indicator field for the Scell DCI, otherwise it is notconsidered. A higher layer (e.g. RRC) indication configuring whether tocount or not count the dormant BWP.

When an Scell PDCCH is used for switching from a regular BWP to dormantBWP, the corresponding scheduled PDSCH can be considered as a nullresource to avoid unnecessary uplink transmission from the UE (HybridAutomatic Repeat Request (HARQ) feedback, etc) since PDSCH cannot beretransmitted (in case HARQ-feedback). It can be disadvantageous to useScell PDCCH for switching from a regular to dormant BWP unless the lastscheduled TBS can be sacrificed (e.g. long delay or dummy). It is muchmore beneficial to use Pcell indication for switching between regularand dormant BWP.

When dormancy is indicated for an Scell, in addition to stopping PDCCHmonitoring, the UE may stop periodic SRS transmissions on the Scell (ifconfigured). To enable this, one option is to create the notion of an ULdormant BWP (e.g. an UL BWP configured without periodic SRS transmissionor periodic SRS transmission with sparse periodicity e.g., periodicitylonger than a predefined value), and a DL dormant BWP (e.g. DL BWPconfigured without PDCCH monitoring) and assume that UE switches to boththe UL dormant BWP and the DL dormant BWP on the Scell when the L1command on the Pcell indicates transition to dormancy.

In some embodiments, a UE does not perform periodic SRS transmissions onan Scell when Pcell indicates transition to dormancy for that Scell. Forexample, by configuring a DL dormant BWP for the Scell and adding a UEprocedure that that SRS transmissions (at least periodic SRStransmissions) are stopped on the SCell when switch to the DL dormantBWP is indicated via the L1 command.

Aperiodic SRS transmissions on the Scell (if triggered by DCI from ascheduling cell other than Scell) may still be performed even when thecurrent active BWP for the Scell is the dormant BWP. In some examples,aperiodic SRS transmissions on a dormant UL BWP of an Scell aretriggered by DCI received on the primary cell.

Configuring a BWP (called dormant BWP) with certain predefinedcharacteristics. Reducing DCI overhead by only considering the BWPs notconfigured as dormant BWP when determining DCI payload size of ‘BWPindicator field’ of an Scell configured with a dormant BWP. Stopping SRStransmissions on an Scell when the DL BWP of the Scell is switched to aBWP designated as a dormant BWP.

In general, when transition to dormant BWP is indicated for an Scell,the UE may stop transmitting periodic SRS on the Scell. No separate ULdormant BWP configuration may be introduced.

The dormant BWP can be configured such that some attributes of thedormant BWP are constrained to be same as those configured for at leastone other BWP configured for the UE.

For example, the dormant BWP can be constrained to have same BW as atleast one other BWP configured for the UE.

In another example, the dormant BWP can be constrained to have one ormore of following parameters to be same as at least one other BWPconfigured for the UE: locationAndBandwidth (e.g. a parameter indicatingthe location and number of frequency domain resource blocks thatcorrespond to the BWP); subcarrierSpacing (e.g. a parameter indicatingthe subcarrier spacing of Orthogonal Frequency Division Multiplex (OFDM)transmissions corresponding to the BWP); cyclicPrefix (e.g. a parameterindicating the cyclic prefix of OFDM transmissions corresponding to theBWP).

In another example, transmissions on the dormant BWP can be assumed tobe constrained such that they follow the same beam, spatial parameters,transmission control indication (TCI) state as that of one at least oneother BWP configured for the UE.

In another example, an explicit higher layer parameter is introduced toindicate the linkage between the dormant BWP and that of one at leastone other BWP configured for the UE with which the dormant BWP sharescertain constraints e.g. same SCS/locationAndBandwidth, cyclicPrefix,etc.

In yet another example, the dormant BWP configuration can explicitlyinclude a higher layer parameter indicating the other BWP that is linkedto the dormant BWP (linkedBWP-Id).

In yet another example, the regular BWP configuration can explicitlyinclude a higher layer parameter flag indicating the regular BWP islinked to the dormant BWP (linkedToDormantBWP).

In an example, for an Scell the transition between dormancy behavior tonon-dormancy behavior means transitioning between dormancy BWP to theother regular BWP with which the dormant BWP is linked. Although thiswould imply a restriction on BWP switching flexibility when there areseveral BWPs, a primary benefit is that a lot of information/processing(CSI/beam management) from dormant BWP is readily available and usablewhen the other regular BWP is activated for data transmission/reception.

In an example, for an Scell, the transition between non-dormancybehavior to dormancy behavior means transitioning between current activeBWP to the dormant BWP.

In some cases, switching delay from/to a dormant BWP to regular BWP canbe based on whether some attributes (e.g. the attributes discussedabove) of the dormant BWP are same as that of the regular BWP. Forexample, if above parameters or TCI state assumptions (e.g., for CSImeasurements) of dormant and regular BWP are same, the switching delaycan be a first value, otherwise it can be a second value larger thanfirst value. In some cases, the first value is smaller than the secondvalue.

The switching delay can be the delay D2 discussed above. The switchingdelay can be a maximum allowed delay for the UE.

If the BWP indicator field in the Scell DCI indicates switching to a BWPidentified as dormant BWP, the UE may discard the PDSCH/PUSCH resourceallocation included in the Scell DCI, and not receive/transmit thecorresponding PDSCH/PUSCH. The UE may transmit any correspondingHARQ-ACK.

If the BWP indicator field in the Scell DCI indicates switching to a BWPidentified as dormant BWP, the corresponding PDSCH/PUSCH resourceallocation and associated fields (e.g., resource allocation) may beindicated as ‘reserved’ in the DCI, for example, the DCI may beinterpreted as not scheduling any data. UE may discard the PDSCH/PUSCHresource allocation included in the Scell DCI, and not receive/transmitthe corresponding PDSCH/PUSCH. The UE may or may not transmit anycorresponding HARQ-ACK. The HARQ-ACK information can provideconfirmation that the switching command was successfully received by theUE. If such confirmation is not considered beneficial, the HARQ-ACKtransmission is not necessary and the corresponding fields in the DCIcould also be considered as reserved.

In one example, if some of the PDCCH search spaces in the dormant BWPare configured with search space periodicity set to inf (infinity), theUE may assume that PDCCH BDs for those search spaces are not requiredfor the SCell when switched to the dormant BWP (e.g., is consideredactive).

A dormant BWP can have an attribute that there is no data or PDSCHscheduling allowed for it (and similarly for uplink, there is no PUSCHscheduling allowed for it), for example, the frequency domain ortime-domain resource allocation field for a dormant BWP is considered asreserved. Still, for dormancy BWP, some minimum configuration related toPDSCH may be needed such as those necessary for ensuring the proper CSImeasurement and reporting, including any potential minimum schedulingoffset configuration for triggering aperiodic CSI-RS transmission,measurement and reporting.

Operations of the wireless device 500 (implemented using the structureof the block diagram of FIG. 5 will now be discussed with reference tothe flow charts of FIGS. 8-11 according to some embodiments of inventiveconcepts. For example, modules may be stored in memory 505 of FIG. 5 ,and these modules may provide instructions so that when the instructionsof a module are executed by respective wireless device processingcircuitry 503, processing circuitry 503 performs respective operationsof the flow charts.

At block 810, processing circuitry 503 receives, via transceiver 501, amessage from a network node instructing the UE to switch to a BWP of aScell.

FIG. 11 depicts an example of the UE receiving a message from thenetwork node instructing the UE to switch to the BWP of the Scell. Atblock 1110, processing circuitry 503 receives, via transceiver 501, anactivation command on a Pcell. At block 1120, processing circuitry 503performs a first set of actions. At block 1130, processing circuitry503, receives a dormant command on the Pcell. At block 1140, processingcircuitry 503, switches to the dormant BWP on the Scell.

Returning to FIG. 8 , at block 820, processing circuitry 503 switches tothe BWP of the Scell.

At block 830, processing circuitry 503 receives, via transceiver 501, aBWP configuration. In some embodiments, the BWP configuration canindicate allowable actions on the BWP. In additional or alternativeembodiments, the BWP configuration can include a field that indicates anID of the BWP and/or whether the BWP is a dormant BWP.

At block 840, processing circuitry 503 determines whether the BWP of theScell of the UE is a dormant BWP. In some embodiments, determiningwhether the BWP of the Scell of the UE is a dormant BWP is based on areceived higher layer parameter in a Scell configuration that indicatesan identifier of the dormant BWP. In additional or alternativeembodiments, determining whether the BWP is a dormant BWP is based onthe BWP configuration. In some examples, processing circuitry 503determines the BWP is a dormant BWP based on the BWP configuration notallowing PDCCH monitoring. In additional or alternative examples,processing circuitry 503 determines the BWP is a dormant BWP based onthe BWP configuration indicating that the BWP is a dormant BWP.

At block 850, processing circuitry 503 determines a set of actionsperformable by the UE based on whether the BWP is a dormant BWP.

At block 860, processing circuitry 503 performs the set of actions.

FIGS. 9-10 depict examples of performing the set of actions. In FIG. 9 ,at block 910, processing circuitry 503 stops PDCCH monitoring. At block920, processing circuitry 503 performs CSI reporting. In FIG. 10 , atblock 1010, processing circuitry 503 stops SRS transmissions. At block1020, processing circuitry 503 performs CSI reporting.

Various operations from the flow chart of FIGS. 8-11 may be optionalwith respect to some embodiments of wireless devices and relatedmethods. Regarding methods of example embodiment 1 (set forth below),for example, operations of blocks 810, 820, 910, 920, 1010, 1020, 1110,1120, 1130, and 1140 of FIGS. 8-11 may be optional.

Operations of a RAN node 600 (implemented using the structure of FIG. 6) will now be discussed with reference to the flow chart of FIG. 12according to some embodiments of inventive concepts. For example,modules may be stored in memory 605 of FIG. 6 , and these modules mayprovide instructions so that when the instructions of a module areexecuted by respective RAN node processing circuitry 603, processingcircuitry 603 performs respective operations of the flow chart.

At block 1210, processing circuitry 603 determines a dormant BWPconfiguration. In some embodiments, determining dormant BWPconfigurations includes determining a set of actions performable by theUE on the dormant BWP.

At block 1220, processing circuitry 603 transmits, via transceiver 601,a command to cause the UE to switch between the dormant BWP and anotherBWP of the Scell. In some embodiments, transmitting the command to causethe UE to switch between the dormant BWP and another BWP of the Scellincludes limiting the UE to performing the set of actions on the dormantBWP. In additional or alternative embodiments, the set of actions doesnot include physical downlink control channel, PDCCH, monitoring or theset of actions includes stopping PDCCH monitoring. In additional oralternative embodiments, transmitting the command to cause the UE toswitch between the dormant BWP and another BWP of the Scell includestransmitting the command on a primary cell, Pcell, of the UE.

In additional or alternative embodiments, the dormant BWP is an uplink,UL, dormant DWP and the dormant BWP configuration is a dormant UL BWPconfiguration. The set of actions does not include performing soundingreference signal, SRS, transmissions or the set of actions includesstopping SRS transmissions.

Although FIG. 12 is described above in regards to a RAN node, anysuitable network node can perform the operations of FIG. 12 . Variousoperations from the flow charts of FIG. 12 may be optional with respectto some embodiments of network nodes and related methods.

Example embodiments are discussed below.

Example 1. A method of operating a user equipment, UE, in a wirelesscommunication network, the method comprising:

-   -   receiving (830) a bandwidth part, BWP, configuration associated        with a BWP of a secondary serving cell, Scell, of the UE;    -   determining (840) whether the BWP of the Scell of the UE is a        dormant BWP based on whether a field of the BWP configuration        indicates the BWP is a dormant BWP;    -   responsive to determining whether the BWP of the Scell is a        dormant BWP, determining (850) a set of actions performable by        the UE based on whether the BWP is a dormant BWP; and    -   performing (860) the set of actions.

Example 2. The method of Example 1, wherein determining whether the BWPof the Scell of the UE is a dormant BWP comprises determining whetherthe BWP configuration allows PDCCH monitoring on the BWP.

Example 3. The method of any of Examples 1-2, wherein determiningwhether the BWP of the Scell of the UE is a dormant BWP comprisesdetermining that the BWP of the Scell of the UE is a dormant BWP, and

-   -   wherein determining the set of actions performable by the UE        based on whether the BWP is a dormant BWP comprises determining        the set of actions performable by the UE based on the BWP being        a dormant BWP.

Example 4. The method of any of Examples 1-3, wherein the set of actionscomprise:

-   -   stopping (910) physical downlink control channel, PDCCH,        monitoring on the Scell.

Example 5. The method of any of Examples 1-4, wherein the set of actionscomprise:

-   -   stopping (1010) sounding reference signal, SRS, transmissions on        the Scell.

Example 6. The method of any of Examples 1-5, wherein the set of actionscomprise:

-   -   performing (920, 1020) CSI reporting for the Scell.

Example 7. The method of any of Examples 1-6, further comprising:

-   -   receiving (810) a message from a network node operating in the        wireless communication network, the message instructing the UE        to switch to the BWP of the Scell; and    -   responsive to receiving the message, switching (850) to the BWP        of the Scell.

Example 8. The method of Example 7, wherein the set of actions comprisesa second set of actions,

-   -   the method further comprising:        -   receiving (1110) an activation command on a primary cell,            Pcell, indicating activation of the Scell;        -   responsive to receiving the activation command, performing            (1120) a first set of actions comprising PDCCH monitoring;        -   receiving (1130) a dormancy indication command on the Pcell            that comprises an indication of the Scell;        -   responsive to receiving the dormancy indication command,            switching (1140) to the dormant BWP on the Scell and            performing the second set of actions.

Example 9. The method of Claim 1-8, wherein determining whether the BWPof the Scell of the UE is a dormant BWP comprises determining that theBWP of the Scell of the UE is a dormant BWP, and

-   -   wherein the BWP configuration of the BWP of the Scell of the UE        is received only when the UE is configured with at least one        other UE-specific BWP configuration.

Example 10. The method of any of Examples 1-9, determining the size of aBWP indicator field of a DCI for the SCell considering only the BWPsthat are not dormant BWPs.

Example 11. The method of any of Examples 1-10, discarding at leastresource allocation for a downlink or an uplink data transmission forthe Scell in a DCI if the DCI also indicates switching to the dormantBWP for the Scell.

Example 12. A method of operating a network node in a wirelesscommunication network, the method comprising:

-   -   determining (1210) a dormant bandwidth part, BWP, configuration        associated with a dormant BWP of a secondary cell, Scell, of a        user equipment, UE; and    -   transmitting (1220) a command to cause the UE to switch between        the dormant BWP and another BWP of the Scell.

Example 13. The method of Example 12, wherein determining dormant BWPconfigurations comprises determining a set of actions performable by theUE on the dormant BWP,

-   -   wherein transmitting the command to cause the UE to switch        between the dormant BWP and another BWP of the Scell comprises        limiting the UE to performing the set of actions on the dormant        BWP.

Example 14. The method of Example 13, wherein the set of actions doesnot comprise physical downlink control channel, PDCCH, monitoring or theset of actions comprises stopping PDCCH monitoring.

Example 15. The method of Example 13, wherein the dormant BWP comprisesa uplink, UL, dormant BWP and the dormant BWP configurations comprisedormant UL BWP configurations,

-   -   wherein the set of actions does not comprise performing sounding        reference signal, SRS, transmissions or the set of actions        comprises stopping SRS transmissions.

Example 16. The method of any of Examples 12-15, wherein transmittingthe command to cause the UE to switch between the dormant BWP andanother BWP of the Scell comprises transmitting the command on a primarycell, Pcell, of the UE.

Example 17. A user equipment, UE, (500) configured to operate in awireless communication network, the UE comprising:

-   -   processing circuitry (503); and    -   memory (505) coupled to the processing circuitry and having        instructions stored therein that are executable by the        processing circuitry to cause the UE to perform operations        comprising:        -   receiving (830) a bandwidth part, BWP, configuration            associated with a BWP of a secondary serving cell, Scell, of            the UE;        -   determining (840) whether the BWP of the Scell of the UE is            a dormant BWP based on a received higher layer parameter in            a Scell configuration that indicates an identifier of the            dormant BWP;        -   responsive to determining whether the BWP of the Scell is a            dormant BWP, determining (850) a set of actions performable            by the UE based on whether the BWP is a dormant BWP; and        -   performing (860) the set of actions.

Example 18. The UE of Example 17, the operations further comprising anyof the operations of Examples 2-11.

Example 19. A network node (600, 700) configured to operate in awireless communication network, the network node comprising:

-   -   processing circuitry (603, 703); and    -   memory (605, 705) coupled to the processing circuitry and having        instructions stored therein that are executable by the        processing circuitry to cause the network node to perform        operations comprising:        -   determining (1210) a dormant bandwidth part, BWP,            configuration associated with a dormant BWP of a secondary            cell, Scell, of a user equipment, UE; and        -   transmitting (1220) a command to cause the UE to switch            between the dormant BWP and another BWP of the Scell.

Example 20. The network node of Example 19, the operations furthercomprising any of the operations of Examples 13-16.

Example 21. A user equipment, UE, (500) configured to operate in awireless communication network, the UE adapted to perform operationscomprising:

-   -   receiving (830) a bandwidth part, BWP, configuration associated        with a BWP of a secondary serving cell, Scell, of the UE;    -   determining (840) whether the BWP of the Scell of the UE is a        dormant BWP based on a received higher layer parameter in a        Scell configuration that indicates an identifier of the dormant        BWP;    -   responsive to determining whether the BWP of the Scell is a        dormant BWP, determining (850) a set of actions performable by        the UE based on whether the BWP is a dormant BWP; and    -   performing (860) the set of actions.

Example 22. The UE of Example 21, further adapted to perform any of theoperations of Examples 2-11.

Example 23. A network node (600, 700) configured to operate in awireless communication network, the network node adapted to performoperations comprising:

-   -   determining (1210) a dormant bandwidth part, BWP, configuration        associated with a dormant BWP of a secondary cell, Scell, of a        user equipment, UE; and    -   transmitting (1220) a command to cause the UE to switch between        the dormant BWP and another BWP of the Scell.

Example 24. The network node of Example 23, further adapted to performany of the operations of Examples 13-16.

Example 25. A computer program comprising program code to be executed byprocessing circuitry (503) of a user equipment, UE, (500) configured tooperate in a wireless communication network, whereby execution of theprogram code causes the UE to perform operations comprising:

-   -   receiving (830) a bandwidth part, BWP, configuration associated        with a BWP of a secondary serving cell, Scell, of the UE;    -   determining (840) whether the BWP of the Scell of the UE is a        dormant BWP based on a received higher layer parameter in a        Scell configuration that indicates an identifier of the dormant        BWP    -   responsive to determining whether the BWP of the Scell is a        dormant BWP, determining (850) a set of actions performable by        the UE based on whether the BWP is a dormant BWP; and    -   performing (860) the set of actions.

Example 26. The computer program of Example 25, the operations furthercomprising any of the operations of Examples 2-11.

Example 27. A computer program comprising program code to be executed byprocessing circuitry (603, 703) of a network node (600, 700) configuredto operate in a wireless communication network, whereby execution of theprogram code causes the network node to perform operations comprising:

-   -   determining (1210) a dormant bandwidth part, BWP, configuration        associated with a dormant BWP of a secondary cell, Scell, of a        user equipment, UE; and    -   transmitting (1220) a command to cause the UE to switch between        the dormant BWP and another BWP of the Scell.

Example 28. The computer program of Example 27, the operations furthercomprising any of the operations of Examples 13-16.

Example 29. A computer program product comprising a non-transitorystorage medium including program code to be executed by processingcircuitry (503) of a user equipment, UE, (500) configured to operate ina wireless communication network, whereby execution of the program codecauses the UE to perform operations comprising:

-   -   receiving (830) a bandwidth part, BWP, configuration associated        with a BWP of a secondary serving cell, Scell, of the UE;    -   determining (840) whether the BWP of the Scell of the UE is a        dormant BWP based on a received higher layer parameter in a        Scell configuration that indicates an identifier of the dormant        BWP;    -   responsive to determining whether the BWP of the Scell is a        dormant BWP, determining (850) a set of actions performable by        the UE based on whether the BWP is a dormant BWP; and    -   performing (860) the set of actions.

Example 30. The computer program product of Example 29, the operationsfurther comprising any of the operations of Examples 2-11.

Example 31. A computer program product comprising a non-transitorystorage medium including program code to be executed by processingcircuitry (603, 703) of a network node (600, 700) configured to operatein a wireless communication network, whereby execution of the programcode causes the network node to perform operations comprising:

-   -   determining (1210) a dormant bandwidth part, BWP, configuration        associated with a dormant BWP of a secondary cell, Scell, of a        user equipment, UE; and    -   transmitting (1220) a command to cause the UE to switch between        the dormant BWP and another BWP of the Scell.

Example 32. The computer program product of Example 31, the operationsfurther comprising any of the operations of Examples 13-16.

Additional explanation is provided below.

Generally, all terms used herein are to be interpreted according totheir ordinary meaning in the relevant technical field, unless adifferent meaning is clearly given and/or is implied from the context inwhich it is used. All references to a/an/the element, apparatus,component, means, step, etc. are to be interpreted openly as referringto at least one instance of the element, apparatus, component, means,step, etc., unless explicitly stated otherwise. The steps of any methodsdisclosed herein do not have to be performed in the exact orderdisclosed, unless a step is explicitly described as following orpreceding another step and/or where it is implicit that a step mustfollow or precede another step. Any feature of any of the embodimentsdisclosed herein may be applied to any other embodiment, whereverappropriate. Likewise, any advantage of any of the embodiments may applyto any other embodiments, and vice versa. Other objectives, features andadvantages of the enclosed embodiments will be apparent from thefollowing description.

Some of the embodiments contemplated herein will now be described morefully with reference to the accompanying drawings. Other embodiments,however, are contained within the scope of the subject matter disclosedherein, the disclosed subject matter should not be construed as limitedto only the embodiments set forth herein; rather, these embodiments areprovided by way of example to convey the scope of the subject matter tothose skilled in the art.

FIG. 13 illustrates a wireless network in accordance with someembodiments.

Although the subject matter described herein may be implemented in anyappropriate type of system using any suitable components, theembodiments disclosed herein are described in relation to a wirelessnetwork, such as the example wireless network illustrated in FIG. 13 .For simplicity, the wireless network of FIG. 13 only depicts network4106, network nodes 4160 and 4160 b, and WDs 4110, 4110 b, and 4110 c(also referred to as mobile terminals). In practice, a wireless networkmay further include any additional elements suitable to supportcommunication between wireless devices or between a wireless device andanother communication device, such as a landline telephone, a serviceprovider, or any other network node or end device. Of the illustratedcomponents, network node 4160 and wireless device (WD) 4110 are depictedwith additional detail. The wireless network may provide communicationand other types of services to one or more wireless devices tofacilitate the wireless devices' access to and/or use of the servicesprovided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type ofcommunication, telecommunication, data, cellular, and/or radio networkor other similar type of system. In some embodiments, the wirelessnetwork may be configured to operate according to specific standards orother types of predefined rules or procedures. Thus, particularembodiments of the wireless network may implement communicationstandards, such as Global System for Mobile Communications (GSM),Universal Mobile Telecommunications System (UMTS), Long Term Evolution(LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless localarea network (WLAN) standards, such as the IEEE 802.11 standards; and/orany other appropriate wireless communication standard, such as theWorldwide Interoperability for Microwave Access (WiMax), Bluetooth,Z-Wave and/or ZigBee standards.

Network 4106 may comprise one or more backhaul networks, core networks,IP networks, public switched telephone networks (PSTNs), packet datanetworks, optical networks, wide-area networks (WANs), local areanetworks (LANs), wireless local area networks (WLANs), wired networks,wireless networks, metropolitan area networks, and other networks toenable communication between devices.

Network node 4160 and WD 4110 comprise various components described inmore detail below. These components work together in order to providenetwork node and/or wireless device functionality, such as providingwireless connections in a wireless network. In different embodiments,the wireless network may comprise any number of wired or wirelessnetworks, network nodes, base stations, controllers, wireless devices,relay stations, and/or any other components or systems that mayfacilitate or participate in the communication of data and/or signalswhether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured,arranged and/or operable to communicate directly or indirectly with awireless device and/or with other network nodes or equipment in thewireless network to enable and/or provide wireless access to thewireless device and/or to perform other functions (e.g., administration)in the wireless network. Examples of network nodes include, but are notlimited to, access points (APs) (e.g., radio access points), basestations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs(eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based onthe amount of coverage they provide (or, stated differently, theirtransmit power level) and may then also be referred to as femto basestations, pico base stations, micro base stations, or macro basestations. A base station may be a relay node or a relay donor nodecontrolling a relay. A network node may also include one or more (orall) parts of a distributed radio base station such as centralizeddigital units and/or remote radio units (RRUs), sometimes referred to asRemote Radio Heads (RRHs). Such remote radio units may or may not beintegrated with an antenna as an antenna integrated radio. Parts of adistributed radio base station may also be referred to as nodes in adistributed antenna system (DAS). Yet further examples of network nodesinclude multi-standard radio (MSR) equipment such as MSR BSs, networkcontrollers such as radio network controllers (RNCs) or base stationcontrollers (BSCs), base transceiver stations (BTSs), transmissionpoints, transmission nodes, multi-cell/multicast coordination entities(MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SONnodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As anotherexample, a network node may be a virtual network node as described inmore detail below. More generally, however, network nodes may representany suitable device (or group of devices) capable, configured, arranged,and/or operable to enable and/or provide a wireless device with accessto the wireless network or to provide some service to a wireless devicethat has accessed the wireless network.

In FIG. 13 , network node 4160 includes processing circuitry 4170,device readable medium 4180, interface 4190, auxiliary equipment 4184,power source 4186, power circuitry 4187, and antenna 4162. Althoughnetwork node 4160 illustrated in the example wireless network of FIG. 13may represent a device that includes the illustrated combination ofhardware components, other embodiments may comprise network nodes withdifferent combinations of components. It is to be understood that anetwork node comprises any suitable combination of hardware and/orsoftware needed to perform the tasks, features, functions and methodsdisclosed herein. Moreover, while the components of network node 4160are depicted as single boxes located within a larger box, or nestedwithin multiple boxes, in practice, a network node may comprise multipledifferent physical components that make up a single illustratedcomponent (e.g., device readable medium 4180 may comprise multipleseparate hard drives as well as multiple RAM modules).

Similarly, network node 4160 may be composed of multiple physicallyseparate components (e.g., a NodeB component and a RNC component, or aBTS component and a BSC component, etc.), which may each have their ownrespective components. In certain scenarios in which network node 4160comprises multiple separate components (e.g., BTS and BSC components),one or more of the separate components may be shared among severalnetwork nodes. For example, a single RNC may control multiple NodeB's.In such a scenario, each unique NodeB and RNC pair, may in someinstances be considered a single separate network node. In someembodiments, network node 4160 may be configured to support multipleradio access technologies (RATs). In such embodiments, some componentsmay be duplicated (e.g., separate device readable medium 4180 for thedifferent RATs) and some components may be reused (e.g., the sameantenna 4162 may be shared by the RATs). Network node 4160 may alsoinclude multiple sets of the various illustrated components fordifferent wireless technologies integrated into network node 4160, suchas, for example, GSM, Wideband Code Division Multiple Access (WCDMA),LTE, NR, WiFi, or Bluetooth wireless technologies. These wirelesstechnologies may be integrated into the same or different chip or set ofchips and other components within network node 4160.

Processing circuitry 4170 is configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being provided by a network node. These operationsperformed by processing circuitry 4170 may include processinginformation obtained by processing circuitry 4170 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedin the network node, and/or performing one or more operations based onthe obtained information or converted information, and as a result ofsaid processing making a determination.

Processing circuitry 4170 may comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software and/or encoded logicoperable to provide, either alone or in conjunction with other networknode 4160 components, such as device readable medium 4180, network node4160 functionality. For example, processing circuitry 4170 may executeinstructions stored in device readable medium 4180 or in memory withinprocessing circuitry 4170. Such functionality may include providing anyof the various wireless features, functions, or benefits discussedherein. In some embodiments, processing circuitry 4170 may include asystem on a chip (SOC).

In some embodiments, processing circuitry 4170 may include one or moreof radio frequency (RF) transceiver circuitry 4172 and basebandprocessing circuitry 4174. In some embodiments, radio frequency (RF)transceiver circuitry 4172 and baseband processing circuitry 4174 may beon separate chips (or sets of chips), boards, or units, such as radiounits and digital units. In alternative embodiments, part or all of RFtransceiver circuitry 4172 and baseband processing circuitry 4174 may beon the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality describedherein as being provided by a network node, base station, eNB or othersuch network device may be performed by processing circuitry 4170executing instructions stored on device readable medium 4180 or memorywithin processing circuitry 4170. In alternative embodiments, some orall of the functionality may be provided by processing circuitry 4170without executing instructions stored on a separate or discrete devicereadable medium, such as in a hard-wired manner. In any of thoseembodiments, whether executing instructions stored on a device readablestorage medium or not, processing circuitry 4170 can be configured toperform the described functionality. The benefits provided by suchfunctionality are not limited to processing circuitry 4170 alone or toother components of network node 4160, but are enjoyed by network node4160 as a whole, and/or by end users and the wireless network generally.

Device readable medium 4180 may comprise any form of volatile ornon-volatile computer readable memory including, without limitation,persistent storage, solid-state memory, remotely mounted memory,magnetic media, optical media, random access memory (RAM), read-onlymemory (ROM), mass storage media (for example, a hard disk), removablestorage media (for example, a flash drive, a Compact Disk (CD) or aDigital Video Disk (DVD)), and/or any other volatile or non-volatile,non-transitory device readable and/or computer-executable memory devicesthat store information, data, and/or instructions that may be used byprocessing circuitry 4170. Device readable medium 4180 may store anysuitable instructions, data or information, including a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry 4170 and, utilized by network node 4160. Devicereadable medium 4180 may be used to store any calculations made byprocessing circuitry 4170 and/or any data received via interface 4190.In some embodiments, processing circuitry 4170 and device readablemedium 4180 may be considered to be integrated.

Interface 4190 is used in the wired or wireless communication ofsignalling and/or data between network node 4160, network 4106, and/orWDs 4110. As illustrated, interface 4190 comprises port(s)/terminal(s)4194 to send and receive data, for example to and from network 4106 overa wired connection. Interface 4190 also includes radio front endcircuitry 4192 that may be coupled to, or in certain embodiments a partof, antenna 4162. Radio front end circuitry 4192 comprises filters 4198and amplifiers 4196. Radio front end circuitry 4192 may be connected toantenna 4162 and processing circuitry 4170. Radio front end circuitrymay be configured to condition signals communicated between antenna 4162and processing circuitry 4170. Radio front end circuitry 4192 mayreceive digital data that is to be sent out to other network nodes orWDs via a wireless connection. Radio front end circuitry 4192 mayconvert the digital data into a radio signal having the appropriatechannel and bandwidth parameters using a combination of filters 4198and/or amplifiers 4196. The radio signal may then be transmitted viaantenna 4162. Similarly, when receiving data, antenna 4162 may collectradio signals which are then converted into digital data by radio frontend circuitry 4192. The digital data may be passed to processingcircuitry 4170. In other embodiments, the interface may comprisedifferent components and/or different combinations of components.

In certain alternative embodiments, network node 4160 may not includeseparate radio front end circuitry 4192, instead, processing circuitry4170 may comprise radio front end circuitry and may be connected toantenna 4162 without separate radio front end circuitry 4192. Similarly,in some embodiments, all or some of RF transceiver circuitry 4172 may beconsidered a part of interface 4190. In still other embodiments,interface 4190 may include one or more ports or terminals 4194, radiofront end circuitry 4192, and RF transceiver circuitry 4172, as part ofa radio unit (not shown), and interface 4190 may communicate withbaseband processing circuitry 4174, which is part of a digital unit (notshown).

Antenna 4162 may include one or more antennas, or antenna arrays,configured to send and/or receive wireless signals. Antenna 4162 may becoupled to radio front end circuitry 4192 and may be any type of antennacapable of transmitting and receiving data and/or signals wirelessly. Insome embodiments, antenna 4162 may comprise one or moreomni-directional, sector or panel antennas operable to transmit/receiveradio signals between, for example, 2 GHz and 66 GHz. Anomni-directional antenna may be used to transmit/receive radio signalsin any direction, a sector antenna may be used to transmit/receive radiosignals from devices within a particular area, and a panel antenna maybe a line of sight antenna used to transmit/receive radio signals in arelatively straight line. In some instances, the use of more than oneantenna may be referred to as MIMO. In certain embodiments, antenna 4162may be separate from network node 4160 and may be connectable to networknode 4160 through an interface or port.

Antenna 4162, interface 4190, and/or processing circuitry 4170 may beconfigured to perform any receiving operations and/or certain obtainingoperations described herein as being performed by a network node. Anyinformation, data and/or signals may be received from a wireless device,another network node and/or any other network equipment. Similarly,antenna 4162, interface 4190, and/or processing circuitry 4170 may beconfigured to perform any transmitting operations described herein asbeing performed by a network node. Any information, data and/or signalsmay be transmitted to a wireless device, another network node and/or anyother network equipment.

Power circuitry 4187 may comprise, or be coupled to, power managementcircuitry and is configured to supply the components of network node4160 with power for performing the functionality described herein. Powercircuitry 4187 may receive power from power source 4186. Power source4186 and/or power circuitry 4187 may be configured to provide power tothe various components of network node 4160 in a form suitable for therespective components (e.g., at a voltage and current level needed foreach respective component). Power source 4186 may either be included in,or external to, power circuitry 4187 and/or network node 4160. Forexample, network node 4160 may be connectable to an external powersource (e.g., an electricity outlet) via an input circuitry or interfacesuch as an electrical cable, whereby the external power source suppliespower to power circuitry 4187. As a further example, power source 4186may comprise a source of power in the form of a battery or battery packwhich is connected to, or integrated in, power circuitry 4187. Thebattery may provide backup power should the external power source fail.Other types of power sources, such as photovoltaic devices, may also beused.

Alternative embodiments of network node 4160 may include additionalcomponents beyond those shown in FIG. 13 that may be responsible forproviding certain aspects of the network node's functionality, includingany of the functionality described herein and/or any functionalitynecessary to support the subject matter described herein. For example,network node 4160 may include user interface equipment to allow input ofinformation into network node 4160 and to allow output of informationfrom network node 4160. This may allow a user to perform diagnostic,maintenance, repair, and other administrative functions for network node4160.

As used herein, wireless device (WD) refers to a device capable,configured, arranged and/or operable to communicate wirelessly withnetwork nodes and/or other wireless devices. Unless otherwise noted, theterm WD may be used interchangeably herein with user equipment (UE).Communicating wirelessly may involve transmitting and/or receivingwireless signals using electromagnetic waves, radio waves, infraredwaves, and/or other types of signals suitable for conveying informationthrough air. In some embodiments, a WD may be configured to transmitand/or receive information without direct human interaction. Forinstance, a WD may be designed to transmit information to a network on apredetermined schedule, when triggered by an internal or external event,or in response to requests from the network. Examples of a WD include,but are not limited to, a smart phone, a mobile phone, a cell phone, avoice over IP (VoIP) phone, a wireless local loop phone, a desktopcomputer, a personal digital assistant (PDA), a wireless cameras, agaming console or device, a music storage device, a playback appliance,a wearable terminal device, a wireless endpoint, a mobile station, atablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mountedequipment (LME), a smart device, a wireless customer-premise equipment(CPE). a vehicle-mounted wireless terminal device, etc. A WD may supportdevice-to-device (D2D) communication, for example by implementing a 3GPPstandard for sidelink communication, vehicle-to-vehicle (V2V),vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may inthis case be referred to as a D2D communication device. As yet anotherspecific example, in an Internet of Things (IoT) scenario, a WD mayrepresent a machine or other device that performs monitoring and/ormeasurements, and transmits the results of such monitoring and/ormeasurements to another WD and/or a network node. The WD may in thiscase be a machine-to-machine (M2M) device, which may in a 3GPP contextbe referred to as an MTC device. As one particular example, the WD maybe a UE implementing the 3GPP narrow band internet of things (NB-IoT)standard. Particular examples of such machines or devices are sensors,metering devices such as power meters, industrial machinery, or home orpersonal appliances (e.g. refrigerators, televisions, etc.) personalwearables (e.g., watches, fitness trackers, etc.). In other scenarios, aWD may represent a vehicle or other equipment that is capable ofmonitoring and/or reporting on its operational status or other functionsassociated with its operation. A WD as described above may represent theendpoint of a wireless connection, in which case the device may bereferred to as a wireless terminal. Furthermore, a WD as described abovemay be mobile, in which case it may also be referred to as a mobiledevice or a mobile terminal.

As illustrated, wireless device 4110 includes antenna 4111, interface4114, processing circuitry 4120, device readable medium 4130, userinterface equipment 4132, auxiliary equipment 4134, power source 4136and power circuitry 4137. WD 4110 may include multiple sets of one ormore of the illustrated components for different wireless technologiessupported by WD 4110, such as, for example, GSM, WCDMA, LTE, NR, WiFi,WiMAX, or Bluetooth wireless technologies, just to mention a few. Thesewireless technologies may be integrated into the same or different chipsor set of chips as other components within WD 4110.

Antenna 4111 may include one or more antennas or antenna arrays,configured to send and/or receive wireless signals, and is connected tointerface 4114. In certain alternative embodiments, antenna 4111 may beseparate from WD 4110 and be connectable to WD 4110 through an interfaceor port. Antenna 4111, interface 4114, and/or processing circuitry 4120may be configured to perform any receiving or transmitting operationsdescribed herein as being performed by a WD. Any information, dataand/or signals may be received from a network node and/or another WD. Insome embodiments, radio front end circuitry and/or antenna 4111 may beconsidered an interface.

As illustrated, interface 4114 comprises radio front end circuitry 4112and antenna 4111. Radio front end circuitry 4112 comprise one or morefilters 4118 and amplifiers 4116. Radio front end circuitry 4112 isconnected to antenna 4111 and processing circuitry 4120, and isconfigured to condition signals communicated between antenna 4111 andprocessing circuitry 4120. Radio front end circuitry 4112 may be coupledto or a part of antenna 4111. In some embodiments, WD 4110 may notinclude separate radio front end circuitry 4112; rather, processingcircuitry 4120 may comprise radio front end circuitry and may beconnected to antenna 4111. Similarly, in some embodiments, some or allof RF transceiver circuitry 4122 may be considered a part of interface4114. Radio front end circuitry 4112 may receive digital data that is tobe sent out to other network nodes or WDs via a wireless connection.Radio front end circuitry 4112 may convert the digital data into a radiosignal having the appropriate channel and bandwidth parameters using acombination of filters 4118 and/or amplifiers 4116. The radio signal maythen be transmitted via antenna 4111. Similarly, when receiving data,antenna 4111 may collect radio signals which are then converted intodigital data by radio front end circuitry 4112. The digital data may bepassed to processing circuitry 4120. In other embodiments, the interfacemay comprise different components and/or different combinations ofcomponents.

Processing circuitry 4120 may comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software, and/or encoded logicoperable to provide, either alone or in conjunction with other WD 4110components, such as device readable medium 4130, WD 4110 functionality.Such functionality may include providing any of the various wirelessfeatures or benefits discussed herein. For example, processing circuitry4120 may execute instructions stored in device readable medium 4130 orin memory within processing circuitry 4120 to provide the functionalitydisclosed herein.

As illustrated, processing circuitry 4120 includes one or more of RFtransceiver circuitry 4122, baseband processing circuitry 4124, andapplication processing circuitry 4126. In other embodiments, theprocessing circuitry may comprise different components and/or differentcombinations of components. In certain embodiments processing circuitry4120 of WD 4110 may comprise a SOC. In some embodiments, RF transceivercircuitry 4122, baseband processing circuitry 4124, and applicationprocessing circuitry 4126 may be on separate chips or sets of chips. Inalternative embodiments, part or all of baseband processing circuitry4124 and application processing circuitry 4126 may be combined into onechip or set of chips, and RF transceiver circuitry 4122 may be on aseparate chip or set of chips. In still alternative embodiments, part orall of RF transceiver circuitry 4122 and baseband processing circuitry4124 may be on the same chip or set of chips, and application processingcircuitry 4126 may be on a separate chip or set of chips. In yet otheralternative embodiments, part or all of RF transceiver circuitry 4122,baseband processing circuitry 4124, and application processing circuitry4126 may be combined in the same chip or set of chips. In someembodiments, RF transceiver circuitry 4122 may be a part of interface4114. RF transceiver circuitry 4122 may condition RF signals forprocessing circuitry 4120.

In certain embodiments, some or all of the functionality describedherein as being performed by a WD may be provided by processingcircuitry 4120 executing instructions stored on device readable medium4130, which in certain embodiments may be a computer-readable storagemedium. In alternative embodiments, some or all of the functionality maybe provided by processing circuitry 4120 without executing instructionsstored on a separate or discrete device readable storage medium, such asin a hard-wired manner. In any of those particular embodiments, whetherexecuting instructions stored on a device readable storage medium ornot, processing circuitry 4120 can be configured to perform thedescribed functionality. The benefits provided by such functionality arenot limited to processing circuitry 4120 alone or to other components ofWD 4110, but are enjoyed by WD 4110 as a whole, and/or by end users andthe wireless network generally.

Processing circuitry 4120 may be configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being performed by a WD. These operations, asperformed by processing circuitry 4120, may include processinginformation obtained by processing circuitry 4120 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedby WD 4110, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Device readable medium 4130 may be operable to store a computer program,software, an application including one or more of logic, rules, code,tables, etc. and/or other instructions capable of being executed byprocessing circuitry 4120. Device readable medium 4130 may includecomputer memory (e.g., Random Access Memory (RAM) or Read Only Memory(ROM)), mass storage media (e.g., a hard disk), removable storage media(e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or anyother volatile or non-volatile, non-transitory device readable and/orcomputer executable memory devices that store information, data, and/orinstructions that may be used by processing circuitry 4120. In someembodiments, processing circuitry 4120 and device readable medium 4130may be considered to be integrated.

User interface equipment 4132 may provide components that allow for ahuman user to interact with WD 4110. Such interaction may be of manyforms, such as visual, audial, tactile, etc. User interface equipment4132 may be operable to produce output to the user and to allow the userto provide input to WD 4110. The type of interaction may vary dependingon the type of user interface equipment 4132 installed in WD 4110. Forexample, if WD 4110 is a smart phone, the interaction may be via a touchscreen; if WD 4110 is a smart meter, the interaction may be through ascreen that provides usage (e.g., the number of gallons used) or aspeaker that provides an audible alert (e.g., if smoke is detected).User interface equipment 4132 may include input interfaces, devices andcircuits, and output interfaces, devices and circuits. User interfaceequipment 4132 is configured to allow input of information into WD 4110,and is connected to processing circuitry 4120 to allow processingcircuitry 4120 to process the input information. User interfaceequipment 4132 may include, for example, a microphone, a proximity orother sensor, keys/buttons, a touch display, one or more cameras, a USBport, or other input circuitry. User interface equipment 4132 is alsoconfigured to allow output of information from WD 4110, and to allowprocessing circuitry 4120 to output information from WD 4110. Userinterface equipment 4132 may include, for example, a speaker, a display,vibrating circuitry, a USB port, a headphone interface, or other outputcircuitry. Using one or more input and output interfaces, devices, andcircuits, of user interface equipment 4132, WD 4110 may communicate withend users and/or the wireless network, and allow them to benefit fromthe functionality described herein.

Auxiliary equipment 4134 is operable to provide more specificfunctionality which may not be generally performed by WDs. This maycomprise specialized sensors for doing measurements for variouspurposes, interfaces for additional types of communication such as wiredcommunications etc. The inclusion and type of components of auxiliaryequipment 4134 may vary depending on the embodiment and/or scenario.

Power source 4136 may, in some embodiments, be in the form of a batteryor battery pack. Other types of power sources, such as an external powersource (e.g., an electricity outlet), photovoltaic devices or powercells, may also be used. WD 4110 may further comprise power circuitry4137 for delivering power from power source 4136 to the various parts ofWD 4110 which need power from power source 4136 to carry out anyfunctionality described or indicated herein. Power circuitry 4137 may incertain embodiments comprise power management circuitry. Power circuitry4137 may additionally or alternatively be operable to receive power froman external power source; in which case WD 4110 may be connectable tothe external power source (such as an electricity outlet) via inputcircuitry or an interface such as an electrical power cable. Powercircuitry 4137 may also in certain embodiments be operable to deliverpower from an external power source to power source 4136. This may be,for example, for the charging of power source 4136. Power circuitry 4137may perform any formatting, converting, or other modification to thepower from power source 4136 to make the power suitable for therespective components of WD 4110 to which power is supplied.

FIG. 14 illustrates a user Equipment in accordance with someembodiments.

FIG. 14 illustrates one embodiment of a UE in accordance with variousaspects described herein. As used herein, a user equipment or UE may notnecessarily have a user in the sense of a human user who owns and/oroperates the relevant device. Instead, a UE may represent a device thatis intended for sale to, or operation by, a human user but which maynot, or which may not initially, be associated with a specific humanuser (e.g., a smart sprinkler controller). Alternatively, a UE mayrepresent a device that is not intended for sale to, or operation by, anend user but which may be associated with or operated for the benefit ofa user (e.g., a smart power meter). UE 42200 may be any UE identified bythe 3rd Generation Partnership Project (3GPP), including a NB-IoT UE, amachine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.UE 4200, as illustrated in FIG. 14 , is one example of a WD configuredfor communication in accordance with one or more communication standardspromulgated by the 3rd Generation Partnership Project (3GPP), such as3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, theterm WD and UE may be used interchangeable. Accordingly, although FIG.14 is a UE, the components discussed herein are equally applicable to aWD, and vice-versa.

In FIG. 14 , UE 4200 includes processing circuitry 4201 that isoperatively coupled to input/output interface 4205, radio frequency (RF)interface 4209, network connection interface 4211, memory 4215 includingrandom access memory (RAM) 4217, read-only memory (ROM) 4219, andstorage medium 4221 or the like, communication subsystem 4231, powersource 4213, and/or any other component, or any combination thereof.Storage medium 4221 includes operating system 4223, application program4225, and data 4227. In other embodiments, storage medium 4221 mayinclude other similar types of information. Certain UEs may utilize allof the components shown in FIG. 14 , or only a subset of the components.The level of integration between the components may vary from one UE toanother UE. Further, certain UEs may contain multiple instances of acomponent, such as multiple processors, memories, transceivers,transmitters, receivers, etc.

In FIG. 14 , processing circuitry 4201 may be configured to processcomputer instructions and data. Processing circuitry 4201 may beconfigured to implement any sequential state machine operative toexecute machine instructions stored as machine-readable computerprograms in the memory, such as one or more hardware-implemented statemachines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logictogether with appropriate firmware; one or more stored program,general-purpose processors, such as a microprocessor or Digital SignalProcessor (DSP), together with appropriate software; or any combinationof the above. For example, the processing circuitry 4201 may include twocentral processing units (CPUs). Data may be information in a formsuitable for use by a computer.

In the depicted embodiment, input/output interface 4205 may beconfigured to provide a communication interface to an input device,output device, or input and output device. UE 4200 may be configured touse an output device via input/output interface 4205. An output devicemay use the same type of interface port as an input device. For example,a USB port may be used to provide input to and output from UE 4200. Theoutput device may be a speaker, a sound card, a video card, a display, amonitor, a printer, an actuator, an emitter, a smartcard, another outputdevice, or any combination thereof. UE 4200 may be configured to use aninput device via input/output interface 4205 to allow a user to captureinformation into UE 4200. The input device may include a touch-sensitiveor presence-sensitive display, a camera (e.g., a digital camera, adigital video camera, a web camera, etc.), a microphone, a sensor, amouse, a trackball, a directional pad, a trackpad, a scroll wheel, asmartcard, and the like. The presence-sensitive display may include acapacitive or resistive touch sensor to sense input from a user. Asensor may be, for instance, an accelerometer, a gyroscope, a tiltsensor, a force sensor, a magnetometer, an optical sensor, a proximitysensor, another like sensor, or any combination thereof. For example,the input device may be an accelerometer, a magnetometer, a digitalcamera, a microphone, and an optical sensor.

In FIG. 14 , RF interface 4209 may be configured to provide acommunication interface to RF components such as a transmitter, areceiver, and an antenna. Network connection interface 4211 may beconfigured to provide a communication interface to network 4243 a.Network 4243 a may encompass wired and/or wireless networks such as alocal-area network (LAN), a wide-area network (WAN), a computer network,a wireless network, a telecommunications network, another like networkor any combination thereof. For example, network 4243 a may comprise aWi-Fi network. Network connection interface 4211 may be configured toinclude a receiver and a transmitter interface used to communicate withone or more other devices over a communication network according to oneor more communication protocols, such as Ethernet, TCP/IP, SONET, ATM,or the like. Network connection interface 4211 may implement receiverand transmitter functionality appropriate to the communication networklinks (e.g., optical, electrical, and the like). The transmitter andreceiver functions may share circuit components, software or firmware,or alternatively may be implemented separately.

RAM 4217 may be configured to interface via bus 4202 to processingcircuitry 4201 to provide storage or caching of data or computerinstructions during the execution of software programs such as theoperating system, application programs, and device drivers. ROM 4219 maybe configured to provide computer instructions or data to processingcircuitry 4201. For example, ROM 4219 may be configured to storeinvariant low-level system code or data for basic system functions suchas basic input and output (I/O), startup, or reception of keystrokesfrom a keyboard that are stored in a non-volatile memory. Storage medium4221 may be configured to include memory such as RAM, ROM, programmableread-only memory (PROM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), magneticdisks, optical disks, floppy disks, hard disks, removable cartridges, orflash drives. In one example, storage medium 4221 may be configured toinclude operating system 4223, application program 4225 such as a webbrowser application, a widget or gadget engine or another application,and data file 4227. Storage medium 4221 may store, for use by UE 4200,any of a variety of various operating systems or combinations ofoperating systems.

Storage medium 4221 may be configured to include a number of physicaldrive units, such as redundant array of independent disks (RAID), floppydisk drive, flash memory, USB flash drive, external hard disk drive,thumb drive, pen drive, key drive, high-density digital versatile disc(HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray opticaldisc drive, holographic digital data storage (HDDS) optical disc drive,external mini-dual in-line memory module (DIMM), synchronous dynamicrandom access memory (SDRAM), external micro-DIMM SDRAM, smartcardmemory such as a subscriber identity module or a removable user identity(SIM/RUIM) module, other memory, or any combination thereof. Storagemedium 4221 may allow UE 4200 to access computer-executableinstructions, application programs or the like, stored on transitory ornon-transitory memory media, to off-load data, or to upload data. Anarticle of manufacture, such as one utilizing a communication system maybe tangibly embodied in storage medium 4221, which may comprise a devicereadable medium.

In FIG. 14 , processing circuitry 4201 may be configured to communicatewith network 4243 b using communication subsystem 4231. Network 4243 aand network 4243 b may be the same network or networks or differentnetwork or networks. Communication subsystem 4231 may be configured toinclude one or more transceivers used to communicate with network 4243b. For example, communication subsystem 4231 may be configured toinclude one or more transceivers used to communicate with one or moreremote transceivers of another device capable of wireless communicationsuch as another WD, UE, or base station of a radio access network (RAN)according to one or more communication protocols, such as IEEE 802.11,CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver mayinclude transmitter 4233 and/or receiver 4235 to implement transmitteror receiver functionality, respectively, appropriate to the RAN links(e.g., frequency allocations and the like). Further, transmitter 4233and receiver 4235 of each transceiver may share circuit components,software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions ofcommunication subsystem 4231 may include data communication, voicecommunication, multimedia communication, short-range communications suchas Bluetooth, near-field communication, location-based communicationsuch as the use of the global positioning system (GPS) to determine alocation, another like communication function, or any combinationthereof. For example, communication subsystem 4231 may include cellularcommunication, Wi-Fi communication, Bluetooth communication, and GPScommunication. Network 4243 b may encompass wired and/or wirelessnetworks such as a local-area network (LAN), a wide-area network (WAN),a computer network, a wireless network, a telecommunications network,another like network or any combination thereof. For example, network4243 b may be a cellular network, a Wi-Fi network, and/or a near-fieldnetwork. Power source 4213 may be configured to provide alternatingcurrent (AC) or direct current (DC) power to components of UE 4200.

The features, benefits and/or functions described herein may beimplemented in one of the components of UE 4200 or partitioned acrossmultiple components of UE 4200. Further, the features, benefits, and/orfunctions described herein may be implemented in any combination ofhardware, software or firmware. In one example, communication subsystem4231 may be configured to include any of the components describedherein. Further, processing circuitry 4201 may be configured tocommunicate with any of such components over bus 4202. In anotherexample, any of such components may be represented by programinstructions stored in memory that when executed by processing circuitry4201 perform the corresponding functions described herein. In anotherexample, the functionality of any of such components may be partitionedbetween processing circuitry 4201 and communication subsystem 4231. Inanother example, the non-computationally intensive functions of any ofsuch components may be implemented in software or firmware and thecomputationally intensive functions may be implemented in hardware.

FIG. 15 illustrates a virtualization environment in accordance with someembodiments.

FIG. 15 is a schematic block diagram illustrating a virtualizationenvironment 4300 in which functions implemented by some embodiments maybe virtualized. In the present context, virtualizing means creatingvirtual versions of apparatuses or devices which may includevirtualizing hardware platforms, storage devices and networkingresources. As used herein, virtualization can be applied to a node(e.g., a virtualized base station or a virtualized radio access node) orto a device (e.g., a UE, a wireless device or any other type ofcommunication device) or components thereof and relates to animplementation in which at least a portion of the functionality isimplemented as one or more virtual components (e.g., via one or moreapplications, components, functions, virtual machines or containersexecuting on one or more physical processing nodes in one or morenetworks).

In some embodiments, some or all of the functions described herein maybe implemented as virtual components executed by one or more virtualmachines implemented in one or more virtual environments 4300 hosted byone or more of hardware nodes 4330. Further, in embodiments in which thevirtual node is not a radio access node or does not require radioconnectivity (e.g., a core network node), then the network node may beentirely virtualized.

The functions may be implemented by one or more applications 4320 (whichmay alternatively be called software instances, virtual appliances,network functions, virtual nodes, virtual network functions, etc.)operative to implement some of the features, functions, and/or benefitsof some of the embodiments disclosed herein. Applications 4320 are runin virtualization environment 4300 which provides hardware 4330comprising processing circuitry 4360 and memory 4390. Memory 4390contains instructions 4395 executable by processing circuitry 4360whereby application 4320 is operative to provide one or more of thefeatures, benefits, and/or functions disclosed herein.

Virtualization environment 4300, comprises general-purpose orspecial-purpose network hardware devices 4330 comprising a set of one ormore processors or processing circuitry 4360, which may be commercialoff-the-shelf (COTS) processors, dedicated Application SpecificIntegrated Circuits (ASICs), or any other type of processing circuitryincluding digital or analog hardware components or special purposeprocessors. Each hardware device may comprise memory 4390-1 which may benon-persistent memory for temporarily storing instructions 4395 orsoftware executed by processing circuitry 4360. Each hardware device maycomprise one or more network interface controllers (NICs) 4370, alsoknown as network interface cards, which include physical networkinterface 4380. Each hardware device may also include non-transitory,persistent, machine-readable storage media 4390-2 having stored thereinsoftware 4395 and/or instructions executable by processing circuitry4360. Software 4395 may include any type of software including softwarefor instantiating one or more virtualization layers 4350 (also referredto as hypervisors), software to execute virtual machines 4340 as well assoftware allowing it to execute functions, features and/or benefitsdescribed in relation with some embodiments described herein.

Virtual machines 4340 comprise virtual processing, virtual memory,virtual networking or interface and virtual storage, and may be run by acorresponding virtualization layer 4350 or hypervisor. Differentembodiments of the instance of virtual appliance 4320 may be implementedon one or more of virtual machines 4340, and the implementations may bemade in different ways.

During operation, processing circuitry 4360 executes software 4395 toinstantiate the hypervisor or virtualization layer 4350, which maysometimes be referred to as a virtual machine monitor (VMM).Virtualization layer 4350 may present a virtual operating platform thatappears like networking hardware to virtual machine 4340.

As shown in FIG. 15 , hardware 4330 may be a standalone network nodewith generic or specific components. Hardware 4330 may comprise antenna43225 and may implement some functions via virtualization.Alternatively, hardware 4330 may be part of a larger cluster of hardware(e.g. such as in a data center or customer premise equipment (CPE))where many hardware nodes work together and are managed via managementand orchestration (MANO) 43100, which, among others, oversees lifecyclemanagement of applications 4320.

Virtualization of the hardware is in some contexts referred to asnetwork function virtualization (NFV). NFV may be used to consolidatemany network equipment types onto industry standard high volume serverhardware, physical switches, and physical storage, which can be locatedin data centers, and customer premise equipment.

In the context of NFV, virtual machine 4340 may be a softwareimplementation of a physical machine that runs programs as if they wereexecuting on a physical, non-virtualized machine. Each of virtualmachines 4340, and that part of hardware 4330 that executes that virtualmachine, be it hardware dedicated to that virtual machine and/orhardware shared by that virtual machine with others of the virtualmachines 4340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) isresponsible for handling specific network functions that run in one ormore virtual machines 4340 on top of hardware networking infrastructure4330 and corresponds to application 4320 in FIG. 15 .

In some embodiments, one or more radio units 43200 that each include oneor more transmitters 43220 and one or more receivers 43210 may becoupled to one or more antennas 43225. Radio units 43200 may communicatedirectly with hardware nodes 4330 via one or more appropriate networkinterfaces and may be used in combination with the virtual components toprovide a virtual node with radio capabilities, such as a radio accessnode or a base station.

In some embodiments, some signalling can be effected with the use ofcontrol system 43230 which may alternatively be used for communicationbetween the hardware nodes 4330 and radio units 43200.

FIG. 16 illustrates a telecommunication network connected via anintermediate network to a host computer in accordance with someembodiments.

With reference to FIG. 16 , in accordance with an embodiment, acommunication system includes telecommunication network 4410, such as a3GPP-type cellular network, which comprises access network 4411, such asa radio access network, and core network 4414. Access network 4411comprises a plurality of base stations 4412 a, 4412 b, 4412 c, such asNBs, eNBs, gNBs or other types of wireless access points, each defininga corresponding coverage area 4413 a, 4413 b, 4413 c. Each base station4412 a, 4412 b, 4412 c is connectable to core network 4414 over a wiredor wireless connection 4415. A first UE 4491 located in coverage area4413 c is configured to wirelessly connect to, or be paged by, thecorresponding base station 4412 c. A second UE 4492 in coverage area4413 a is wirelessly connectable to the corresponding base station 4412a. While a plurality of UEs 4491, 4492 are illustrated in this example,the disclosed embodiments are equally applicable to a situation where asole UE is in the coverage area or where a sole UE is connecting to thecorresponding base station 4412.

Telecommunication network 4410 is itself connected to host computer4430, which may be embodied in the hardware and/or software of astandalone server, a cloud-implemented server, a distributed server oras processing resources in a server farm. Host computer 4430 may beunder the ownership or control of a service provider, or may be operatedby the service provider or on behalf of the service provider.Connections 4421 and 4422 between telecommunication network 4410 andhost computer 4430 may extend directly from core network 4414 to hostcomputer 4430 or may go via an optional intermediate network 4420.Intermediate network 4420 may be one of, or a combination of more thanone of, a public, private or hosted network; intermediate network 4420,if any, may be a backbone network or the Internet; in particular,intermediate network 4420 may comprise two or more sub-networks (notshown).

The communication system of FIG. 16 as a whole enables connectivitybetween the connected UEs 4491, 4492 and host computer 4430. Theconnectivity may be described as an over-the-top (OTT) connection 4450.Host computer 4430 and the connected UEs 4491, 4492 are configured tocommunicate data and/or signaling via OTT connection 4450, using accessnetwork 4411, core network 4414, any intermediate network 4420 andpossible further infrastructure (not shown) as intermediaries. OTTconnection 4450 may be transparent in the sense that the participatingcommunication devices through which OTT connection 4450 passes areunaware of routing of uplink and downlink communications. For example,base station 4412 may not or need not be informed about the past routingof an incoming downlink communication with data originating from hostcomputer 4430 to be forwarded (e.g., handed over) to a connected UE4491. Similarly, base station 4412 need not be aware of the futurerouting of an outgoing uplink communication originating from the UE 4491towards the host computer 4430.

FIG. 17 illustrates a host computer communicating via a base stationwith a user equipment over a partially wireless connection in accordancewith some embodiments.

Example implementations, in accordance with an embodiment, of the UE,base station and host computer discussed in the preceding paragraphswill now be described with reference to FIG. 17 . In communicationsystem 4500, host computer 4510 comprises hardware 4515 includingcommunication interface 4516 configured to set up and maintain a wiredor wireless connection with an interface of a different communicationdevice of communication system 4500. Host computer 4510 furthercomprises processing circuitry 4518, which may have storage and/orprocessing capabilities. In particular, processing circuitry 4518 maycomprise one or more programmable processors, application-specificintegrated circuits, field programmable gate arrays or combinations ofthese (not shown) adapted to execute instructions. Host computer 4510further comprises software 4511, which is stored in or accessible byhost computer 4510 and executable by processing circuitry 4518. Software4511 includes host application 4512. Host application 4512 may beoperable to provide a service to a remote user, such as UE 4530connecting via OTT connection 4550 terminating at UE 4530 and hostcomputer 4510. In providing the service to the remote user, hostapplication 4512 may provide user data which is transmitted using OTTconnection 4550.

Communication system 4500 further includes base station 4520 provided ina telecommunication system and comprising hardware 4525 enabling it tocommunicate with host computer 4510 and with UE 4530. Hardware 4525 mayinclude communication interface 4526 for setting up and maintaining awired or wireless connection with an interface of a differentcommunication device of communication system 4500, as well as radiointerface 4527 for setting up and maintaining at least wirelessconnection 4570 with UE 4530 located in a coverage area (not shown inFIG. 17 ) served by base station 4520. Communication interface 4526 maybe configured to facilitate connection 4560 to host computer 4510.Connection 4560 may be direct or it may pass through a core network (notshown in FIG. 17 ) of the telecommunication system and/or through one ormore intermediate networks outside the telecommunication system. In theembodiment shown, hardware 4525 of base station 4520 further includesprocessing circuitry 4528, which may comprise one or more programmableprocessors, application-specific integrated circuits, field programmablegate arrays or combinations of these (not shown) adapted to executeinstructions. Base station 4520 further has software 4521 storedinternally or accessible via an external connection.

Communication system 4500 further includes UE 4530 already referred to.Its hardware 4535 may include radio interface 4537 configured to set upand maintain wireless connection 4570 with a base station serving acoverage area in which UE 4530 is currently located. Hardware 4535 of UE4530 further includes processing circuitry 4538, which may comprise oneor more programmable processors, application-specific integratedcircuits, field programmable gate arrays or combinations of these (notshown) adapted to execute instructions. UE 4530 further comprisessoftware 4531, which is stored in or accessible by UE 4530 andexecutable by processing circuitry 4538. Software 4531 includes clientapplication 4532. Client application 4532 may be operable to provide aservice to a human or non-human user via UE 4530, with the support ofhost computer 4510. In host computer 4510, an executing host application4512 may communicate with the executing client application 4532 via OTTconnection 4550 terminating at UE 4530 and host computer 4510. Inproviding the service to the user, client application 4532 may receiverequest data from host application 4512 and provide user data inresponse to the request data. OTT connection 4550 may transfer both therequest data and the user data. Client application 4532 may interactwith the user to generate the user data that it provides.

It is noted that host computer 4510, base station 4520 and UE 4530illustrated in FIG. 17 may be similar or identical to host computer4430, one of base stations 4412 a, 4412 b, 4412 c and one of UEs 4491,4492 of FIG. 16 , respectively. This is to say, the inner workings ofthese entities may be as shown in FIG. 17 and independently, thesurrounding network topology may be that of FIG. 16 .

In FIG. 17 , OTT connection 4550 has been drawn abstractly to illustratethe communication between host computer 4510 and UE 4530 via basestation 4520, without explicit reference to any intermediary devices andthe precise routing of messages via these devices. Networkinfrastructure may determine the routing, which it may be configured tohide from UE 4530 or from the service provider operating host computer4510, or both. While OTT connection 4550 is active, the networkinfrastructure may further take decisions by which it dynamicallychanges the routing (e.g., on the basis of load balancing considerationor reconfiguration of the network).

Wireless connection 4570 between UE 4530 and base station 4520 is inaccordance with the teachings of the embodiments described throughoutthis disclosure. One or more of the various embodiments may improve theperformance of OTT services provided to UE 4530 using OTT connection4550, in which wireless connection 4570 forms the last segment. Moreprecisely, the teachings of these embodiments may improve the randomaccess speed and/or reduce random access failure rates and therebyprovide benefits such as faster and/or more reliable random access.

A measurement procedure may be provided for the purpose of monitoringdata rate, latency and other factors on which the one or moreembodiments improve. There may further be an optional networkfunctionality for reconfiguring OTT connection 4550 between hostcomputer 4510 and UE 4530, in response to variations in the measurementresults. The measurement procedure and/or the network functionality forreconfiguring OTT connection 4550 may be implemented in software 4511and hardware 4515 of host computer 4510 or in software 4531 and hardware4535 of UE 4530, or both. In embodiments, sensors (not shown) may bedeployed in or in association with communication devices through whichOTT connection 4550 passes; the sensors may participate in themeasurement procedure by supplying values of the monitored quantitiesexemplified above, or supplying values of other physical quantities fromwhich software 4511, 4531 may compute or estimate the monitoredquantities. The reconfiguring of OTT connection 4550 may include messageformat, retransmission settings, preferred routing etc.; thereconfiguring need not affect base station 4520, and it may be unknownor imperceptible to base station 4520. Such procedures andfunctionalities may be known and practiced in the art. In certainembodiments, measurements may involve proprietary UE signalingfacilitating host computer 4510's measurements of throughput,propagation times, latency and the like. The measurements may beimplemented in that software 4511 and 4531 causes messages to betransmitted, in particular empty or ‘dummy’ messages, using OTTconnection 4550 while it monitors propagation times, errors etc.

FIG. 18 illustrates methods implemented in a communication systemincluding a host computer, a base station and a user equipment inaccordance with some embodiments.

FIG. 18 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 16-17 . Forsimplicity of the present disclosure, only drawing references to FIG. 18will be included in this section. In step 4610, the host computerprovides user data. In substep 4611 (which may be optional) of step4610, the host computer provides the user data by executing a hostapplication. In step 4620, the host computer initiates a transmissioncarrying the user data to the UE. In step 4630 (which may be optional),the base station transmits to the UE the user data which was carried inthe transmission that the host computer initiated, in accordance withthe teachings of the embodiments described throughout this disclosure.In step 4640 (which may also be optional), the UE executes a clientapplication associated with the host application executed by the hostcomputer.

FIG. 19 illustrates methods implemented in a communication systemincluding a host computer, a base station and a user equipment inaccordance with some embodiments.

FIG. 19 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 16-17 . Forsimplicity of the present disclosure, only drawing references to FIG. 19will be included in this section. In step 4710 of the method, the hostcomputer provides user data. In an optional substep (not shown) the hostcomputer provides the user data by executing a host application. In step4720, the host computer initiates a transmission carrying the user datato the UE. The transmission may pass via the base station, in accordancewith the teachings of the embodiments described throughout thisdisclosure. In step 4730 (which may be optional), the UE receives theuser data carried in the transmission.

FIG. 20 illustrates methods implemented in a communication systemincluding a host computer, a base station and a user equipment inaccordance with some embodiments

FIG. 20 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 16-17 . Forsimplicity of the present disclosure, only drawing references to FIG. 20will be included in this section. In step 4810 (which may be optional),the UE receives input data provided by the host computer. Additionallyor alternatively, in step 4820, the UE provides user data. In substep4821 (which may be optional) of step 4820, the UE provides the user databy executing a client application. In substep 4811 (which may beoptional) of step 4810, the UE executes a client application whichprovides the user data in reaction to the received input data providedby the host computer. In providing the user data, the executed clientapplication may further consider user input received from the user.Regardless of the specific manner in which the user data was provided,the UE initiates, in substep 4830 (which may be optional), transmissionof the user data to the host computer. In step 4840 of the method, thehost computer receives the user data transmitted from the UE, inaccordance with the teachings of the embodiments described throughoutthis disclosure.

FIG. 21 illustrates methods implemented in a communication systemincluding a host computer, a base station and a user equipment inaccordance with some embodiments

FIG. 21 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 16-17 . Forsimplicity of the present disclosure, only drawing references to FIG. 21will be included in this section. In step 4910 (which may be optional),in accordance with the teachings of the embodiments described throughoutthis disclosure, the base station receives user data from the UE. Instep 4920 (which may be optional), the base station initiatestransmission of the received user data to the host computer. In step4930 (which may be optional), the host computer receives the user datacarried in the transmission initiated by the base station.

Any appropriate steps, methods, features, functions, or benefitsdisclosed herein may be performed through one or more functional unitsor modules of one or more virtual apparatuses. Each virtual apparatusmay comprise a number of these functional units. These functional unitsmay be implemented via processing circuitry, which may include one ormore microprocessor or microcontrollers, as well as other digitalhardware, which may include digital signal processors (DSPs),special-purpose digital logic, and the like. The processing circuitrymay be configured to execute program code stored in memory, which mayinclude one or several types of memory such as read-only memory (ROM),random-access memory (RAM), cache memory, flash memory devices, opticalstorage devices, etc. Program code stored in memory includes programinstructions for executing one or more telecommunications and/or datacommunications protocols as well as instructions for carrying out one ormore of the techniques described herein. In some implementations, theprocessing circuitry may be used to cause the respective functional unitto perform corresponding functions according one or more embodiments ofthe present disclosure.

The term unit may have conventional meaning in the field of electronics,electrical devices and/or electronic devices and may include, forexample, electrical and/or electronic circuitry, devices, modules,processors, memories, logic solid state and/or discrete devices,computer programs or instructions for carrying out respective tasks,procedures, computations, outputs, and/or displaying functions, and soon, as such as those that are described herein.

Further definitions and embodiments are discussed below.

In the above-description of various embodiments of present inventiveconcepts, it is to be understood that the terminology used herein is forthe purpose of describing particular embodiments only and is notintended to be limiting of present inventive concepts. Unless otherwisedefined, all terms (including technical and scientific terms) usedherein have the same meaning as commonly understood by one of ordinaryskill in the art to which present inventive concepts belong. It will befurther understood that terms, such as those defined in commonly useddictionaries, should be interpreted as having a meaning that isconsistent with their meaning in the context of this specification andthe relevant art and will not be interpreted in an idealized or overlyformal sense unless expressly so defined herein.

When an element is referred to as being “connected”, “coupled”,“responsive”, or variants thereof to another element, it can be directlyconnected, coupled, or responsive to the other element or interveningelements may be present. In contrast, when an element is referred to asbeing “directly connected”, “directly coupled”, “directly responsive”,or variants thereof to another element, there are no interveningelements present. Like numbers refer to like elements throughout.Furthermore, “coupled”, “connected”, “responsive”, or variants thereofas used herein may include wirelessly coupled, connected, or responsive.As used herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. Well-known functions or constructions may not be described indetail for brevity and/or clarity. The term “and/or” (abbreviated “/)includes any and all combinations of one or more of the associatedlisted items.

It will be understood that although the terms first, second, third, etc.may be used herein to describe various elements/operations, theseelements/operations should not be limited by these terms. These termsare only used to distinguish one element/operation from anotherelement/operation. Thus a first element/operation in some embodimentscould be termed a second element/operation in other embodiments withoutdeparting from the teachings of present inventive concepts. The samereference numerals or the same reference designators denote the same orsimilar elements throughout the specification.

As used herein, the terms “comprise”, “comprising”, “comprises”,“include”, “including”, “includes”, “have”, “has”, “having”, or variantsthereof are open-ended, and include one or more stated features,integers, elements, steps, components or functions but does not precludethe presence or addition of one or more other features, integers,elements, steps, components, functions or groups thereof. Furthermore,as used herein, the common abbreviation “e.g.”, which derives from theLatin phrase “exempli gratia,” may be used to introduce or specify ageneral example or examples of a previously mentioned item, and is notintended to be limiting of such item. The common abbreviation “i.e.”,which derives from the Latin phrase “id est,” may be used to specify aparticular item from a more general recitation.

Example embodiments are described herein with reference to blockdiagrams and/or flowchart illustrations of computer-implemented methods,apparatus (systems and/or devices) and/or computer program products. Itis understood that a block of the block diagrams and/or flowchartillustrations, and combinations of blocks in the block diagrams and/orflowchart illustrations, can be implemented by computer programinstructions that are performed by one or more computer circuits. Thesecomputer program instructions may be provided to a processor circuit ofa general purpose computer circuit, special purpose computer circuit,and/or other programmable data processing circuit to produce a machine,such that the instructions, which execute via the processor of thecomputer and/or other programmable data processing apparatus, transformand control transistors, values stored in memory locations, and otherhardware components within such circuitry to implement thefunctions/acts specified in the block diagrams and/or flowchart block orblocks, and thereby create means (functionality) and/or structure forimplementing the functions/acts specified in the block diagrams and/orflowchart block(s).

These computer program instructions may also be stored in a tangiblecomputer-readable medium that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablemedium produce an article of manufacture including instructions whichimplement the functions/acts specified in the block diagrams and/orflowchart block or blocks. Accordingly, embodiments of present inventiveconcepts may be embodied in hardware and/or in software (includingfirmware, resident software, micro-code, etc.) that runs on a processorsuch as a digital signal processor, which may collectively be referredto as “circuitry,” “a module” or variants thereof.

It should also be noted that in some alternate implementations, thefunctions/acts noted in the blocks may occur out of the order noted inthe flowcharts. For example, two blocks shown in succession may in factbe executed substantially concurrently or the blocks may sometimes beexecuted in the reverse order, depending upon the functionality/actsinvolved. Moreover, the functionality of a given block of the flowchartsand/or block diagrams may be separated into multiple blocks and/or thefunctionality of two or more blocks of the flowcharts and/or blockdiagrams may be at least partially integrated. Finally, other blocks maybe added/inserted between the blocks that are illustrated, and/orblocks/operations may be omitted without departing from the scope ofinventive concepts. Moreover, although some of the diagrams includearrows on communication paths to show a primary direction ofcommunication, it is to be understood that communication may occur inthe opposite direction to the depicted arrows.

Many variations and modifications can be made to the embodiments withoutsubstantially departing from the principles of the present inventiveconcepts. All such variations and modifications are intended to beincluded herein within the scope of present inventive concepts.Accordingly, the above disclosed subject matter is to be consideredillustrative, and not restrictive, and the examples of embodiments areintended to cover all such modifications, enhancements, and otherembodiments, which fall within the spirit and scope of present inventiveconcepts. Thus, to the maximum extent allowed by law, the scope ofpresent inventive concepts are to be determined by the broadestpermissible interpretation of the present disclosure including theexamples of embodiments and their equivalents, and shall not berestricted or limited by the foregoing detailed description.

1-32. (canceled)
 33. A method performed by a user equipment, UE, in awireless communication network, the UE being configured with at least afirst UE-specific radio resource control configured bandwidth part, BWP,of a secondary serving cell, Scell, of the UE, the method comprising:receiving at least a second BWP, configuration associated with a BWP ofthe Scell, of the UE; and determining whether the first or the at leastsecond BWP is a dormant BWP based on a received higher layer parameterin an Scell configuration that indicates a BWP identifier of the atleast first or second BWP as the dormant BWP.
 34. The method of claim33, wherein the Scell configuration comprises a dormantBWP-Id field of aServingCellConfig information to indicate the BWP which is the dormantBWP.
 35. The method of claim 33, further comprising: receiving a messagefrom a network node operating in the wireless communication network, themessage instructing the UE to switch to the BWP of the Scell; andresponsive to receiving the message, switching to the BWP of the Scell,wherein the BWP is determined as the dormant BWP.
 36. The method ofclaim 35, further comprising: determining a set of actions performableby the UE based on the BWP being determined as the dormant BWP; andperforming the set of actions.
 37. The method of claim 33, wherein theset of actions comprises a second set of actions, the method furthercomprising: receiving (1110) an activation command on a primary cell,Pcell, indicating activation of the Scell; responsive to receiving theactivation command, performing a first set of actions comprising PDCCHmonitoring; receiving a dormancy indication command on the Pcell thatcomprises an indication of the Scell; responsive to receiving thedormancy indication command, switching to the BWP identified as thedormant BWP on the Scell and performing the second set of actions. 38.The method of claim 33, determining the size of a BWP indicator field ofa DCI for the SCell considering only the BWPs that are not dormant BWPs.39. The method of claim 33, discarding at least a resource allocationfor a downlink or an uplink data transmission for the Scell in a DCI ifthe DCI also indicates switching to the dormant BWP for the Scell.
 40. Amethod performed by a network node in a wireless communication network,the method comprising: configuring a UE with at least a firstUE-specific radio resource control configured bandwidth part, BWP, of asecondary serving cell, Scell, of the UE; identifying one of the atleast a first BWP or a second BWP of the Scell as a dormant bandwidthpart, BWP; and transmitting a command to cause the UE to switch betweenthe BWP identified as the dormant BWP and another BWP of the Scell. 41.The method of claim 40, wherein identifying the dormant BWP comprisessignaling the BWP Id in a dormantBWP-Id field of a ServingCellConfiginformation.
 42. The method of claim 40, wherein the command comprises adormancy indication command to cause the UE to switch the BWP identifiedas the dormant BWP and transmitting the command on a primary cell,Pcell, of the UE.
 43. A user equipment, UE, configured to operate in awireless communication network, the UE being configured with at least afirst UE-specific radio resource control configured bandwidth part, BWP,of a secondary serving cell, Scell, of the UE, the UE comprising:processing circuitry; and memory coupled to the processing circuitry andhaving instructions stored therein that are executable by the processingcircuitry to cause the UE to perform operations comprising: receiving atleast a second a bandwidth part, BWP, configuration associated with aBWP of the Scell, of the UE; determining whether the first or the atleast second BWP is a dormant BWP based on a received higher layerparameter in an Scell configuration that indicates an identifier of theat least first or second BWP as the dormant BWP.
 44. The UE of claim 43,wherein the Scell configuration comprises a dormantBWP-Id field of aServingCellConfig information to indicate the BWP which is the dormantBWP.
 45. A network node configured to operate in a wirelesscommunication network, the network node comprising: processingcircuitry; and memory coupled to the processing circuitry and havinginstructions stored therein that are executable by the processingcircuitry to cause the network node to perform operations comprising:configuring a UE with at least a first UE-specific radio resourcecontrol configured bandwidth part, BWP, of a secondary serving cell,Scell, of the UE; identifying one of the at least a first BWP or asecond BWP of the Scell as a dormant bandwidth part, BWP; andtransmitting a command to cause the UE to switch between the BWPidentified as the dormant BWP and another BWP of the Scell.
 46. Thenetwork node of claim 45, wherein determining the dormant BWP comprisessignaling the BWP Id in a dormantBWP-Id field of a ServingCellConfiginformation.
 47. A computer program or program product comprisingprogram code to be executed by processing circuitry of a user equipment,UE, or a network node whereby execution of the program code causes theUE or the network node to perform the operation according to claim 33.48. A computer program or program product comprising program code to beexecuted by processing circuitry of a user equipment, UE, or a networknode whereby execution of the program code causes the UE or the networknode to perform the operation according to claim 40.